Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Date: 2011-03-01 21:07:25
Message-ID: 4D6D600D.6020008@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/01/2011 03:53 PM, Jan Urbański wrote:
> On 01/03/11 21:35, Tom Lane wrote:
>> Josh Berkus<josh(at)agliodbs(dot)com> writes:
>>> I'm ok with closing things as of the end of the 15 days, say Thursday or
>>> Friday.
>> It might be a good idea to make a list of what we have left to do before
>> we can wrap an alpha. Here are some things on my list. Not all of them
>> are necessarily release blockers, but we need to discuss which ones are:
>>
>> * Regression test failures from recent plpython patches. These are
>> affecting enough machines to make them "must fix before alpha", IMO.
>> There are some variations in error message wording, which are not too
>> terrible but also not exactly hard to fix. The python assert failure
>> that some Fedora machines are reporting is considerably more disturbing.

I agree.

> I'm looking into the crash, no luck so long.
>
>

Is there anything you need that would help you?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-03-01 21:12:16 Re: pl/python tracebacks
Previous Message Peter Eisentraut 2011-03-01 21:06:52 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)