Prev: [HACKERS] PG 9.0 release timetable
Next: : CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up
From: "Marc G. Fournier" on 31 May 2010 09:52
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,
when most bugs will be reported (and hopefully fixed) relatively quickly
after a beta is released ... RC should be held to a more 'release
standard', but beta's should be closer to a snapshot standard, with a more
short/fixed timeframe so that debuggers aren't hitting the same bugs that
were reported (and fixed), weeks earlier ...

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy(a)hub.org http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org

--
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:37
"Marc G. Fournier" <scrappy(a)hub.org> writes:
> On Mon, 31 May 2010, Bruce Momjian wrote:
>> Well, they can just grab nightly snapshots and test, right? I don't
>> think a beta is fundamentally different from a nightly snapshot,
>> source-code wise.

> doesn't really give a good reference point for testing purposes ...

It's also inferior from a documentation standpoint --- we don't update
the release notes nightly.

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  | 
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