Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Date
Msg-id AANLkTimBW=AA1EHUpbukbSzaRAkEuPpz0TxUgW9VhcUp@mail.gmail.com
Whole thread Raw
In response to Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
List pgsql-hackers
On Mon, Mar 7, 2011 at 2:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> At the risk of hijacking this thread to talk about the subject of this
>> thread, when are we going to cut alpha4?
>
> Well, a prerequisite for cutting an alpha is closing the commitfest,
> which at this point reduces to deciding what we are going to do with
> the plpython traceback patch.
>
> Other than that, I think we're pretty close.

AFAIK, there's nothing particularly special about that patch, other
than that the author chose to move it back from Returned with Feedback
to some other status.  I think we should just pick a time to wrap some
time in the next day or two, and it either makes it or it doesn't.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Next
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: If recovery_target_timeline is set to 'latest' and standby mode