EOL for 8.2 (was Re: Formatting Curmudgeons WAS: MMAP Buffers) - Mailing list pgsql-hackers

From Tom Lane
Subject EOL for 8.2 (was Re: Formatting Curmudgeons WAS: MMAP Buffers)
Date
Msg-id 25048.1303405155@sss.pgh.pa.us
Whole thread Raw
In response to Re: Formatting Curmudgeons WAS: MMAP Buffers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: EOL for 8.2 (was Re: Formatting Curmudgeons WAS: MMAP Buffers)  (Dave Page <dpage@pgadmin.org>)
Re: EOL for 8.2 (was Re: Formatting Curmudgeons WAS: MMAP Buffers)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
[ man, this thread has totally outlived its title, could we change that? I'll start with this subtopic ]

Robert Haas <robertmhaas@gmail.com> writes:
> In fact, I've been wondering if we shouldn't consider extending the
> support window for 8.2 past the currently-planned December 2011.
> There seem to be quite a lot of people running that release precisely
> because the casting changes in 8.3 were so painful, and I think the
> incremental effort on our part to extend support for another year
> would be reasonably small.  I guess the brunt of the work would
> actually fall on the packagers.  It looks like we've done 5 point
> releases of 8.2.x in the last year, so presumably if we did decide to
> extend the EOL date by a year or so that's about how much incremental
> effort would be needed.

I agree that the incremental effort would not be so large, but what
makes you think that the situation will change given another year?
My expectation is that'd just mean people will do nothing about
migrating for a year longer.

More generally: it took a lot of argument to establish the current EOL
policy, and bending it the first time anyone feels any actual pain
will pretty much destroy the whole concept.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: fsync reliability
Next
From: Andres Freund
Date:
Subject: Re: Formatting Curmudgeons WAS: MMAP Buffers