Обсуждение: PostgreSQL 11 Release Management Team & Feature Freeze
Hi,
The Release Management Team (RMT) for the PostgreSQL 11 release
has been assembled and has determined that the feature freeze date
for the PostgreSQL 11 release will be April 7, 2018. This means that any
feature that will be going into the PostgreSQL 11 release must be
committed before 2018-04-08 00:00:00 GMT.
The exception to this is any patches related to bootstrap data [1] which is
purposefully being committed later on. After the freeze is in effect, any
open feature in the current Commitfest will be moved into the subsequent
one.
Open items for the PostgreSQL 11 release will be tracked here:
For the PostgreSQL 11 release, the release management team is composed
of:
Alvaro Herrera <alvherre@alvh.no-ip.org>
Andres Freund <andres@anarazel.de>
Jonathan Katz <jkatz@postgresql.org>
For the time being, if you have any questions about the process, please
feel free to email any member of the RMT. We will send out notes with
updates and additional guidance in the near future.
Thanks!
On Tue, Mar 27, 2018 at 9:51 AM, Jonathan S. Katz <jkatz@postgresql.org> wrote: > The Release Management Team (RMT) for the PostgreSQL 11 release > has been assembled and has determined that the feature freeze date > for the PostgreSQL 11 release will be April 7, 2018. This means that any > feature that will be going into the PostgreSQL 11 release must be > committed before 2018-04-08 00:00:00 GMT. Hmm. I just realized that this is a tad ambiguous/surprising. It looks at like the freeze goes into effect at the *end* of April 7th, not the beginning. Am I reading that correctly? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Apr 6, 2018, at 6:53 PM, Robert Haas <robertmhaas@gmail.com> wrote:On Tue, Mar 27, 2018 at 9:51 AM, Jonathan S. Katz <jkatz@postgresql.org> wrote:The Release Management Team (RMT) for the PostgreSQL 11 release
has been assembled and has determined that the feature freeze date
for the PostgreSQL 11 release will be April 7, 2018. This means that any
feature that will be going into the PostgreSQL 11 release must be
committed before 2018-04-08 00:00:00 GMT.
Hmm. I just realized that this is a tad ambiguous/surprising. It
looks at like the freeze goes into effect at the *end* of April 7th,
not the beginning.
Am I reading that correctly?
Yes. It follows the format from the previous ones, i.e:
Jonathan
On Fri, Apr 6, 2018 at 6:54 PM, Jonathan S. Katz <jkatz@postgresql.org> wrote: > Yes. It follows the format from the previous ones, i.e: > > https://www.postgresql.org/message-id/CA+TgmoY56w5FOzeEo+i48qehL+BsVTwy-Q1M0xjUhUCwgGW7-Q@mail.gmail.com I think my confusion resulted from the fact that my 2016 message said "must be committed no later than XXX" whereas yours says that the feature freeze date is XXX. But no worries - thanks for clarifying. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
> On Apr 6, 2018, at 6:57 PM, Robert Haas <robertmhaas@gmail.com> wrote: > > On Fri, Apr 6, 2018 at 6:54 PM, Jonathan S. Katz <jkatz@postgresql.org> wrote: >> Yes. It follows the format from the previous ones, i.e: >> >> https://www.postgresql.org/message-id/CA+TgmoY56w5FOzeEo+i48qehL+BsVTwy-Q1M0xjUhUCwgGW7-Q@mail.gmail.com > > I think my confusion resulted from the fact that my 2016 message said > "must be committed no later than XXX" whereas yours says that the > feature freeze date is XXX. > > But no worries - thanks for clarifying. Noted for next year. Best of luck to everyone over the next 24hrs! Jonathan
On Fri, Apr 6, 2018 at 6:59 PM, Jonathan S. Katz <jkatz@postgresql.org> wrote: > Best of luck to everyone over the next 24hrs! I think that's the wrong sentiment, honestly. I think we have too many committers relying way too much on luck already. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company