"Joshua D. Drake" <[EMAIL PROTECTED]> 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.
It's not like people have to stop using it the moment we do our
last release.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
