On fre, 2010-01-22 at 18:05 -0500, Robert Haas wrote: > and start talking about > how we can create an environment where patch authors can get their > work committed reasonably quickly (assuming it's good, of course) and > released within some reasonable time frame after that (like, say, > within a year from commit) - because I think those things are > important to the health of the project, and even though FWIH things > are much better than in pre-CommitFest days, I still think there's > quite a bit of room for improvement. > > Any ideas?
The lower bound on the release cycle is about 12 months right now because we intend to support old versions for 5 years, and 5 or 6 branches at once is about the most anyone can handle. That formula is tough to change. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
