The Postgres release team has decided that last year's appointment
of a Release Management Team worked pretty well, so we're going to
run the version-10 release cycle the same way. The members of the
RMT for this year will be Peter Eisentraut, Robert Haas, and Noah
As previously agreed at the PGCon 2016 developers meeting, we'll
institute v10 feature freeze at the completion of the current
commitfest (end of this month). The RMT will target making the
10beta1 release in mid-May and 10.0 final release in September.
Attached for reference is the RMT charter as agreed to by the
regards, tom lane
== Proposed Release Management Team Charter
This charter takes effect on 2017-03-31 and expires three weeks after the
PostgreSQL 10 final release.
- Meet the deadlines pgsql-release@ sets for beta1 and final release.
- When the open items list has an unowned item, promptly inform the associated
committer that he owns that item.
- Approve the creation of REL10_STABLE, the welcoming of PostgreSQL 11
submissions, and the resumption of CommitFests.
- Nag item owners to ensure forward progress.
Powers, exercisable by majority vote of the RMT, even in the face of no
consensus or contrary consensus:
- Approve the commit of a patch for the purpose of resolving an open item,
including reversion commits.
- Add or remove open items.
- Enact a feature freeze.
Before using one of those powers, the Release Management Team (RMT) should
make more than zero effort to let normal community processes arrive at a
sufficient answer. Given the aggressive schedule, the RMT may nonetheless use
these powers quickly and often.
pgsql-release@ appoints the RMT and has the power to dissolve it.
Members are Peter Eisentraut, Robert Haas, and Noah Misch.
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: