Re: PostgreSQL 18 Release Management Team & Feature Freeze
От | Aleksander Alekseev |
---|---|
Тема | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
Дата | |
Msg-id | CAJ7c6TNkS61ubiq4h2JsYh8TNBn5=8Hc37T0Kec3RXG3_9yPXQ@mail.gmail.com обсуждение исходный текст |
Ответ на | PostgreSQL 18 Release Management Team & Feature Freeze (Heikki Linnakangas <hlinnaka@iki.fi>) |
Ответы |
Re: PostgreSQL 18 Release Management Team & Feature Freeze
Re: PostgreSQL 18 Release Management Team & Feature Freeze |
Список | 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
В списке pgsql-hackers по дате отправления: