| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, David Rowley <dgrowleyml(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: PostgreSQL 17 Release Management Team & Feature Freeze |
| Date: | 2024-04-08 14:42:39 |
| Message-ID: | C75E0E6E-9F1F-4A88-B501-E22C6EB42B2E@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 8 Apr 2024, at 17:26, Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:
>
> What if we pick the actual feature freeze time randomly? That is,
> starting on March 15th (or whenever but more than a week before), each
> night someone from RMT generates a random number between $current_day
> and April 8th. If the number matches $current_day, that day at
> midnight is the feature freeze.
But this implies that actual date is not publicly known before feature freeze is in effect. Do I understand idea correctly?
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-04-08 14:42:41 | Re: PostgreSQL 17 Release Management Team & Feature Freeze |
| Previous Message | Laurenz Albe | 2024-04-08 14:42:05 | Re: PostgreSQL 17 Release Management Team & Feature Freeze |