On Tue, Jun 12, 2012 at 09:38:54AM +0100, Simon Riggs wrote:
> On 11 June 2012 18:02, Joshua Berkus <josh@agliodbs.com> wrote:
>
> > Hmmm. I was assuming September, given how late the beta came out,
> > and that nobody has previously talked seriously about a June
> > release. I'll also point out that while there's a beta2 tarball,
> > there was no announcement and no packages for it.
> >
> > If we decide to do June, then PR will be minimal because I was
> > assuming I had another 7 weeks to prepare it. Not that that
> > should be the deciding factor (it would be great to get out an
> > early release and get it out of the way) but it should be taken
> > into consideration.
>
>
> Not really sure why we're discussing it.
>
> We've always had a long beta cycle and this seems to cut it very
> short at both ends.
I'm not sure I understand how having a long beta cycle is a good
thing, or even whether you're saying it is. Could you please clarify?
> If we're going to have a fixed cutoff date for patches then having a
> variable release date seems weird, unless it is to elongate it to fix
> bugs.
>
> Let me put it this way: is there a benefit to changing the plan?
Sure. If it's ready to go, there's no point holding it back.
Downstream projects get a little extra integration time, etc.
> Anyone desperate for the new features is already using them, and we're
> relying upon that to throw up bugs during beta.
I'm always grateful to those brave souls who "go there" with versions
of PostgreSQL that aren't even beta. They're a big chunk of why it
might well be OK to step toward this major release :)
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
