Re: PostgreSQL 17 Release Management Team & Feature Freeze
От | David Rowley |
---|---|
Тема | Re: PostgreSQL 17 Release Management Team & Feature Freeze |
Дата | |
Msg-id | CAApHDvoCZpsB3L=QPKDCpPR9W2rN=XaPngCoHxOkNn-Byp1+cQ@mail.gmail.com обсуждение исходный текст |
Ответ на | PostgreSQL 17 Release Management Team & Feature Freeze (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: PostgreSQL 17 Release Management Team & Feature Freeze
|
Список | pgsql-hackers |
On Mon, 18 Mar 2024 at 15:50, Michael Paquier <michael@paquier.xyz> wrote: > Additionally, the RMT has set the feature freeze to be **April 8, 2024 > at 0:00 AoE** (see [1]). This is the last time to commit features for > PostgreSQL 17. In other words, no new PostgreSQL 17 feature can be > committed after April 8, 2024 at 0:00 AoE. As mentioned last year in > [2], this uses the "standard" feature freeze date/time. Someone asked me about this, so thought it might be useful to post here. To express this as UTC, It's: postgres=# select '2024-04-08 00:00-12:00' at time zone 'UTC'; timezone --------------------- 2024-04-08 12:00:00 Or, time remaining, relative to now: select '2024-04-08 00:00-12:00' - now(); David > [1]: https://en.wikipedia.org/wiki/Anywhere_on_Earth > [2]: https://www.postgresql.org/message-id/9fbe60ec-fd1b-6ee0-240d-af7fc444223d@postgresql.org
В списке pgsql-hackers по дате отправления: