On Wed, Jan 20, 2016 at 8:32 PM, Michael Paquier <michael.paqu...@gmail.com> wrote: > Perhaps some people are more interested in implementing new > features than working on bugs and would just continue hacking and > arguing about new features, at least a stability period may attract > more committer attention into actual bug fixes, in short: no new > features can be committed until the previous versions has reached at > least beta2, rc, whatever. This may accelerate the stability process.
Or it might just accelerate the amount of time it takes to *declare* having reached that milestone. Besides, do you really think that people need to be able to commit something before seriously working on it? Rules that are expressly coercive are a *bad* idea. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
