On Fri, Jun 5, 2015 at 2:50 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > Agreed. Cleanup can occur while we release code for public testing.
The code is available for public testing right now. Stamping it a beta implies that we think it's something fairly stable that we'd be pretty happy to release if things go well, which is a higher bar to clear. I can't help noticing for all the drumbeat of "let's release 9.5 beta now", activity to clean up the items on this list seems quite sluggish: https://wiki.postgresql.org/wiki/PostgreSQL_9.5_Open_Items I've seen Tom and a few other people doing some work that I would describe as useful pre-beta stabilization, but I think there is a good bit more that could be done, and that list is a good starting point. I hope to have time to do some myself, but right now I am busy trying to stabilize 9.3, along with Alvaro, Noah, Andres, and Thomas Munro, and PGCon is coming up in just over a week. I think we could afford to give ourselves at least until a few weeks following PGCon to tidy up. I do agree that an indefinite development freeze with unclear parameters for resuming development and unclear goals is a bad plan. But I think giving ourselves a little more time to, say, turn the buildfarm consistently green, and, say, fix the known but currently-unfixed multixact bugs, and, say, fix the known bugs in 9.5 features is a good plan, and I hope you and others will support it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
