Bruce Momjian <br...@momjian.us> wrote: > here is the ideal schedule: > > Jan 15 start commitfest > Feb 15 stop commitfest > Apr 1 start beta > Jun 1 release release candidate (RC) > Jun 20 release 8.5 > Of course we rarely have an ideal schedule So for a project which strives for an annual release, we have over six months from initial submission of a *small* patch until the release it goes in, if we meet the ideal schedule? Longer for large patches or if we slip from the ideal schedule? That sounds like there are still some opportunities for improvements in project management, but it's not *so* bad if development for the next release can overlap the tail end of that schedule. I'm not sure how much that is anticipated or encouraged, though. It also seems to call into question the wisdom of annual releases. If we had a two-year cycle which had three times as much in it, would that be an improvement, or not? -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
