Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59
Date
Msg-id 6871.1202154261@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> To avoid double-patching effort.  I think we'll branch fairly shortly,
>> like in a week or so, but right now it'd mostly just create make-work
>> for committers.

> Was that a big problem last release?

Well, basically this happens at core's discretion, and we all feel that
waiting a bit more will minimize work.  If there were a lot of people
chomping at the bit to start committing 8.4-only stuff, maybe we'd
decide differently.  But right now what's on my radar screen is still
8.3 bugs, eg the open patch for bug #3921, and we're expecting a few
more new reports as soon as 8.3.0 spreads.

As best I recall, the immediate branch after 8.2 was the exception not
the rule --- we've usually waited longer than that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: configurability of OOM killer
Next
From: Jeff Davis
Date:
Subject: Re: FW: bitemporal functionality for PostgreSQL