Re: do we need to postpone beta4? - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: do we need to postpone beta4?
Date
Msg-id 1280254663.27165.1454.camel@jd-desktop.unknown.charter.com
Whole thread Raw
In response to Re: do we need to postpone beta4?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 2010-07-27 at 14:11 -0400, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > I think we should consider postponing beta4.  I count eleven
> > non-documentation, 9.0-specific bug fix on REL9_0_STABLE, but there
> > are currently five items on the open 9.0 issues list, at least one of
> > which appears to be a new bug in 9.0, and we just got a bug report on
> > pgsql-bugs from Valentine Gogichashvili complaining of what looks to
> > be a crasher in the redo path for heap_xlog_update().  It seems
> > unlikely at this point that we can have all of these issues fixed and
> > still have time for a full buildfarm cycle before the wrap.  Does it
> > make sense to put out a beta with known bugs (presumably requiring
> > another beta) at this point, or should we push this off a bit?
>
> If we don't wrap a beta this week, the next possible window is several
> weeks away, because various people will be on vacation.  So I think we
> should get the existing fixes out there, even if there are known bugs
> remaining.  A beta is not an RC.

If we document the bugs, then +1, if we don't -1. E.g; we let people
know where we KNOW there are warts.

JD

>
>             regards, tom lane
>

--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: page corruption on 8.3+ that makes it to standby
Next
From: Andrew Dunstan
Date:
Subject: Re: PostGIS vs. PGXS in 9.0beta3