Prev: [HACKERS] PG 9.0 release timetable
Next: : CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up
From: Thom Brown on 31 May 2010 09:22
On 31 May 2010 09:33, Simon Riggs <simon(a)2ndquadrant.com> wrote:
>
> We're currently at 4 weeks since last beta, with no new beta in sight.

My understanding was beta 2 would be out on 7th June. Is that changing?

Thom

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Dave Page on 31 May 2010 10:14
On Mon, May 31, 2010 at 2:22 PM, Thom Brown <thombrown(a)gmail.com> wrote:
> On 31 May 2010 09:33, Simon Riggs <simon(a)2ndquadrant.com> wrote:
>>
>> We're currently at 4 weeks since last beta, with no new beta in sight.
>
> My understanding was beta 2 would be out on 7th June.  Is that changing?

No. It's very much in sight on my calendar :-)

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 31 May 2010 10:43
On Mon, 2010-05-31 at 15:14 +0100, Dave Page wrote:
> On Mon, May 31, 2010 at 2:22 PM, Thom Brown <thombrown(a)gmail.com> wrote:
> > On 31 May 2010 09:33, Simon Riggs <simon(a)2ndquadrant.com> wrote:
> >>
> >> We're currently at 4 weeks since last beta, with no new beta in sight.
> >
> > My understanding was beta 2 would be out on 7th June. Is that changing?
>
> No. It's very much in sight on my calendar :-)

Can we make it 2 weeks per beta from now on?

That will allow us to get to Beta5 by 19 Jul, which will hopefully
become RC1 on 2 Aug and then release on 16 Aug.

At the current pace we will be on BETA3 on 12 July, increasing the
probablity of delay, or reducing the number of bugs discovered prior to
release.

If that's a problem, do we need to release BetaN on all platforms? Where
do the majority of bug reports originate? Let's focus there.

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 31 May 2010 11:08
"Marc G. Fournier" <scrappy(a)hub.org> writes:
> On Mon, 31 May 2010, Thom Brown wrote:
>> On 31 May 2010 09:33, Simon Riggs <simon(a)2ndquadrant.com> wrote:
>>> We're currently at 4 weeks since last beta, with no new beta in sight.
>>
>> My understanding was beta 2 would be out on 7th June. Is that changing?

> Yes, but Simon is correct in that 4-5 weeks between betas is a long time,

The reason it went like that is that (a) we had PGCon in there, and (b)
we had a set of security releases in there. Asking for another beta
to have happened is pointless. You might recall that I already *did*
ask that --- I wanted beta2 to happen concurrently with the security
releases --- and was turned down.

I find myself entirely unimpressed by proposals to make releases
according to some rigid schedule that takes no account of whether
packaging manpower is actually available.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 31 May 2010 11:10
Simon Riggs <simon(a)2ndQuadrant.com> writes:
> We're currently at 4 weeks since last beta, with no new beta in sight.

Eh?
http://archives.postgresql.org/pgsql-hackers/2010-05/msg01649.php
You can hardly claim to have not seen it.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: [HACKERS] PG 9.0 release timetable
Next: : CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up