From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(at)vondra(dot)me>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Subject: | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
Date: | 2025-04-10 11:57:28 |
Message-ID: | CAJ7c6TNkS61ubiq4h2JsYh8TNBn5=8Hc37T0Kec3RXG3_9yPXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> We are pleased to announce the Release Management Team (RMT) (cc'd) for
> the PostgreSQL 18 release:
>
> - Tomas Vondra
> - Nathan Bossart
> - Heikki Linnakangas
>
> You can find information about the responsibilities of the RMT here:
> https://wiki.postgresql.org/wiki/Release_Management_Team
>
> We have now entered the feature freeze period. That means that no new
> features will committed for v18 anymore. I ask everyone to focus on
> testing the new features that got in, documentation, and fixes for old
> and new bugs.
>
> You can track open items for the PostgreSQL 18 release here:
> https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items
>
> Please let us know if you have any questions.
Let me be the first author this year who asks to squeeze his patch in
after feature freeze :D
Do you think that it's worth merging SLRU refactoring into PG18, or is
it considered a feature? [1] This is arguably not the top priority and
we could wait for another year but merging it now doesn't seem to be
too much of a burden either.
[1]: https://commitfest.postgresql.org/patch/5250/
--
Best regards,
Aleksander Alekseev
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2025-04-10 12:11:00 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
Previous Message | Aleksander Alekseev | 2025-04-10 11:48:11 | Re: pgsql: Add function to get memory context stats for processes |