| Lists: | pgsql-hackers |
|---|
| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | PostgreSQL 16 Release Management Team & Feature Freeze |
| Date: | 2023-03-21 15:35:16 |
| Message-ID: | 9fbe60ec-fd1b-6ee0-240d-af7fc444223d@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Hi,
We are pleased to announce the Release Management Team (RMT) (cc'd) for
the PostgreSQL 16 release:
- Alvaro Herrera
- Amit Kapila
- Jonathan Katz
You can find information about the responsibilities of the RMT here:
https://wiki.postgresql.org/wiki/Release_Management_Team
Additionally, the RMT has set the feature freeze to be **April 8, 2023
at 0:00 AoE**[1]. This is the last time to commit features for
PostgreSQL 16. In other words, no new PostgreSQL 16 feature can be
committed after April 8, 2023 at 0:00 AoE.
You can track open items for the PostgreSQL 16 release here:
https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items
Finally, the Release Team is considering making April 8 0:00 AoE the
standard feature freeze date/time for future years. This has been the
cutoff over the past several years, and standardizing will give
predictability to when the feature development cycle ends. If you have
reasons why this should not be the case, please voice your concerns.
Please let us know if you have any questions.
On behalf of the PG16 RMT,
Jonathan
| From: | Roberto Mello <roberto(dot)mello(at)gmail(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: PostgreSQL 16 Release Management Team & Feature Freeze |
| Date: | 2023-03-21 17:17:41 |
| Message-ID: | CAKz==bKzRoW5ouLKG6ApA+KB9JrOCj8Sd=jLJFR82rSrS3dMjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Tue, Mar 21, 2023 at 9:35 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>
> You can track open items for the PostgreSQL 16 release here:
>
> https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items
The wiki page references April 8th, 2022, btw.
Roberto
| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Roberto Mello <roberto(dot)mello(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: PostgreSQL 16 Release Management Team & Feature Freeze |
| Date: | 2023-03-21 17:54:01 |
| Message-ID: | f52e3210-8bf8-31c9-33d0-6cd1ab14c583@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On 3/21/23 1:17 PM, Roberto Mello wrote:
> On Tue, Mar 21, 2023 at 9:35 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>>
>> You can track open items for the PostgreSQL 16 release here:
>>
>> https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items
>
> The wiki page references April 8th, 2022, btw.
Fixed :) Thanks!
Jonathan
| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: PostgreSQL 16 Release Management Team & Feature Freeze |
| Date: | 2023-04-06 21:37:39 |
| Message-ID: | 1d4932dc-e520-5c8a-febc-6ab7b45d7a54@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On 3/21/23 11:35 AM, Jonathan S. Katz wrote:
> Additionally, the RMT has set the feature freeze to be **April 8, 2023
> at 0:00 AoE**[1]. This is the last time to commit features for
> PostgreSQL 16. In other words, no new PostgreSQL 16 feature can be
> committed after April 8, 2023 at 0:00 AoE.
This is a reminder that feature freeze is rapidly approach. The freeze
begins at April 8, 2023 at 0:00 AoE. No new PostgreSQL 16 features can
be committed after this time.
Thanks,
Jonathan
| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: PostgreSQL 16 Release Management Team & Feature Freeze |
| Date: | 2023-04-08 12:29:42 |
| Message-ID: | 6cd1a8ad-6cd3-84f1-b3f0-e0af6a125293@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On 4/6/23 5:37 PM, Jonathan S. Katz wrote:
> On 3/21/23 11:35 AM, Jonathan S. Katz wrote:
>
>> Additionally, the RMT has set the feature freeze to be **April 8, 2023
>> at 0:00 AoE**[1]. This is the last time to commit features for
>> PostgreSQL 16. In other words, no new PostgreSQL 16 feature can be
>> committed after April 8, 2023 at 0:00 AoE.
>
> This is a reminder that feature freeze is rapidly approach. The freeze
> begins at April 8, 2023 at 0:00 AoE. No new PostgreSQL 16 features can
> be committed after this time.
The feature freeze for PostgreSQL 16 has begun.
Thank you everyone for all of your hard work and contributions towards
this release! Now we can begin to prepare for the beta period.
Thanks,
Jonathan