From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Stamp 9.1.8. |
Date: | 2013-02-04 21:48:25 |
Message-ID: | CA+OCxoyz-98Y=3Q8DNhS4MUdYUkJgYZBDFY=B9-V7hfS=xVwkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Mon, Feb 4, 2013 at 9:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On 4 February 2013 21:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Stamp 9.1.8.
>
>> Did you not get my mail about me being in the middle of backpatching?
>
>> I guess I can stop now.
>
> 4pm on the day of a release is way too late to be committing anything
> (except security stuff ...). If you felt you had a must-fix problem,
> you should have been lobbying for a release postponement at least
> six hours ago.
We should really freeze the code for 24 hours shouldn't we? That way
we know most, if not all of the buildfarm animals will have had a
chance to go red since the last code change.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-02-04 21:49:31 | Re: pgsql: Stamp 9.1.8. |
Previous Message | Tom Lane | 2013-02-04 21:40:42 | Re: pgsql: Stamp 9.1.8. |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-02-04 21:49:31 | Re: pgsql: Stamp 9.1.8. |
Previous Message | Tom Lane | 2013-02-04 21:40:42 | Re: pgsql: Stamp 9.1.8. |