| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: open items |
| Date: | 2024-05-17 00:11:00 |
| Message-ID: | ZkaglM5C4NGFku09@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 14, 2024 at 09:52:35AM -0400, Robert Haas wrote:
> We are down to three open items, all of which have proposed fixes.
> That is great, but we need to keep things moving along, because
> according to https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items
> we are due to release beta1 on May 23. That means that a release
> freeze will be in effect from Saturday, May 18, which is four days
> from now. Since committing patches sometimes leads to unexpected
> surprises, it would be best if the proposed fixes were put into place
> sooner rather than later, to allow time for any adjustments that may
> be required.
As of this minute, the open item list is empty @-(at)(dot)
Thanks all for the various resolutions, updates and commits!
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-05-17 00:45:59 | Re: Why does pgindent's README say to download typedefs.list from the buildfarm? |
| Previous Message | Jeff Davis | 2024-05-17 00:09:55 | Re: optimizing pg_upgrade's once-in-each-database steps |