| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: Releasing in September |
| Date: | 2016-01-20 16:53:32 |
| Message-ID: | CA+TgmoZDkv7j4o5OKN=CqHkW9_-6d0OH4CW1Z9KLTsrb+qtP4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 20, 2016 at 11:19 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I do not think commitfest length is the problem (though surely it's not
> working as intended). What happened with 9.5 is we forked the 9.6
> development branch on June 30th, with the expectation of releasing in
> September, and then couldn't release in September because nobody had done
> any significant amount of stabilization work. Instead we had the 2015-07
> commitfest. And the 2015-09 commitfest. And the 2015-11 commitfest.
But I'm not very sure that we're talking about the same set of people
here. If we're going to go to a system where nobody's allowed to
commit anything for the next release until the current release is
finalized, then we'd better have some procedure for making sure that
happens relatively quickly. And the procedure can't be that the
people who are hot to get started on the next release have to bat
cleanup for the people who don't have time to fix the bugs they
introduced previously. Because *that* would be manifestly unfair.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-01-20 16:56:44 | Re: Releasing in September |
| Previous Message | Bruce Momjian | 2016-01-20 16:51:17 | Re: Releasing in September |