Re: Do we really need a 7.4.22 release now? - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Do we really need a 7.4.22 release now?
Date
Msg-id 48D26AF3.4020003@hagander.net
Whole thread Raw
In response to Re: Do we really need a 7.4.22 release now?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> Greg Sabino Mullane wrote:
>>> I'm all for killing 7.4, but that's a rather short time frame, especially as
>>> this is a busy time of year for many businesses. How about we make it further
>>> in the future (perhaps 2009-07-01, six months into the next year), and announce
>>> the change far and wide?
> 
>> I believe a single quarter gap is plenty in consideration of the age. It 
>> isn't like 7.4 isn't already really old. If this was 8.0 I would agree.
> 
> The handwriting has been on the wall for 7.4 ever since we agreed that
> 7.3 would be EOL'd at five years...
> 
> I wasn't intending to start a discussion about how/when to EOL 7.4,
> but since the thread has gone in that direction: my vote would be to
> announce now (say, with the announcement of this set of releases) that
> 7.4 will be EOL'd with our first set of updates in 2009.  That would
> probably be the next update after this one, maybe two updates away
> if we find any really serious bugs in the next month or two.

While I agree with the principle, I think the people who care about such
things would need a date, and not just "whenever we do an update". This
could be Jan 2nd or Dec 29th for all they know.

I think it's better to set a date, and then we can push out a final 7.4
release on that day if there are any accumulated changes.

//Magnus



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: WIP patch: Collation support
Next
From: Simon Riggs
Date:
Subject: Re: Subtransaction commits and Hot Standby