From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Stamp 9.1.8. |
Date: | 2013-02-04 22:12:23 |
Message-ID: | 51103247.5080105@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 02/04/2013 04:49 PM, Simon Riggs wrote:
> On 4 February 2013 21:40, 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.
> These timings might mean something to you, but I've never been aware
> of such things because I'm not on the packagers list and its pure
> silence everywhere else.
>
I agree it can be hard to keep the dates in mind. Could we add a couple
of reminders for committers to the release procedures? Say 48 hours
before the release to say "the tree needs to go quiet in 24 hours" and
24 hours before to say "no commits without discussion until the release
is cut"?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-02-04 22:13:01 | Re: pgsql: Stamp 9.1.8. |
Previous Message | Simon Riggs | 2013-02-04 21:54:01 | Re: pgsql: Stamp 9.1.8. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-02-04 22:13:01 | Re: pgsql: Stamp 9.1.8. |
Previous Message | Jeff Janes | 2013-02-04 21:59:57 | Re: autovacuum not prioritising for-wraparound tables |