Re: pgsql: Stamp 9.1.8.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Stamp 9.1.8.
Date: 2013-02-04 22:28:10
Message-ID: CA+U5nMJ370rKQCTeeQcvWuMgmcw=dKzSedg9VoF9CVm-_YTzLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 4 February 2013 22:13, 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:48, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>> 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.
>
>> Do whatever you like, as long as you tell me about it.
>
> No, the problem here is *you* didn't tell anybody what you were doing.

Yes I did, I told hackers I was backpatching fixes and later I told
you. Did I follow your timing rules? No, because I've never heard of
them before and didn't know exact deadlines.

Not really clear why there's so much secrecy, but as long as there is,
don't expect me to follow the secret rules and don't dare accuse me of
pushing boundaries because I tried to fix a bug while your invisible
hour-glass ran out.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-02-05 04:14:51 Re: pgsql: Stamp 9.1.8.
Previous Message Tom Lane 2013-02-04 22:13:01 Re: pgsql: Stamp 9.1.8.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-02-04 22:32:18 Re: issues with range types, btree_gist and constraints
Previous Message Tom Lane 2013-02-04 22:27:39 Re: split rm_name and rm_desc out of rmgr.c