On Thu, Apr 11, 2013 at 11:42:27AM -0400, Tom Lane wrote: > Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > > Tom Lane wrote: > >> The issue with event triggers causing catalog access during START > >> TRANSACTION is clearly a "must fix before beta" item. I'm afraid > >> that bug #8049 is going to require some nontrivial planner changes > >> (more about that in a bit), which means I'd like to get that into > >> the beta cycle too. What else are people aware of? > >> > >> Also, I'd say we need at least draft-quality release notes before > >> we can start beta, else beta testers won't know what to test. > > > Maybe we should release an alpha with current git + draft release notes? > > I would think that all three of the above-mentioned items could be > resolved in parallel, rather than doing one first. (I assume Bruce > hasn't got anything ready release-note-wise.) > > Somebody previously suggested targeting the week of the 22nd for beta > (ie, wrap beta1 on Monday 4/22), and that still seems like it could > work, if there are no bigger problems than these.
I can have release notes ready for April 22 --- I will get started. I think all our major features are committed. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
