On 2016-01-20 11:19:28 -0500, Tom Lane wrote: > We will not get back to on-schedule releases unless we can keep -hackers > working on release testing/stabilization when it's time to do that, > rather than being distracted by shiny new stuff going into the next > release.
Agreed. I'll note that the linux kernel used to have a similar problem. Now there's a two week integration and a 10 week stabilization period, with occasionally a week added/subtracted. If a feature patch is submitted for integration (not just parallel review) into the main branch outside the merge window you get yelled at. Now, we're at least two magnitudes smaller, so not everything there applies to us. But I think looking over that fence, to see how they scaled from smaller where we are now, to way way bigger, isn't a bad idea. I think one thing we should work on, is being absolutely religious about requiring, say, 2 reviews for every nontrivial contribution. We currently seem to have a significantly increased submission rate, and at the same time the number of reviews per patch has gone down substantially. I think the "honor" system has failed in that regard. Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
