From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Nearing beta? |
Date: | 2013-04-11 15:48:08 |
Message-ID: | 20130411154808.GC6057@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 11, 2013 at 11:42:27AM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2013-04-11 15:48:23 | Re: [GSOC] questions about idea "rewrite pg_dump as library" |
Previous Message | Tom Lane | 2013-04-11 15:44:29 | Re: Nearing beta? |