On Sat, 2009-12-05 at 15:33 -0500, Tom Lane wrote:
> In any case there's no need for someone to move off a version instantly
> the day after the last release for it. So I really don't see why you
> think there would be "panic updates".
Hmm, well, I wasn't imagining it as a wholly rational respon
Simon Riggs writes:
> Could I request we change these dates slightly to
The intent of the policy is that the last formal minor release for a
branch will happen no earlier than the specified times. It might well
be later, since we're not going to schedule updates specially for this
--- it'd be wh
On Fri, 2009-12-04 at 16:36 +, Dave Page wrote:
> End Of Life (EOL) dates:
>
> Version EOL Date
> PostgreSQL 7.4July 2010 (extended)
> PostgreSQL 8.0July 2010 (extended)
> PostgreSQL 8.1November 2010
> PostgreSQL 8.2December 2011
> Postgre
On Fri, Dec 4, 2009 at 5:27 PM, Andres Freund wrote:
> Hi,
>
> On Friday 04 December 2009 17:36:00 Dave Page wrote:
>> Version EOL Date
>> PostgreSQL 7.4 July 2010 (extended)
>> PostgreSQL 8.0 July 2010 (extended)
>> PostgreSQL 8.1 November 2010
>> Postgr
Hi,
On Friday 04 December 2009 17:36:00 Dave Page wrote:
> Version EOL Date
> PostgreSQL 7.4July 2010 (extended)
> PostgreSQL 8.0July 2010 (extended)
> PostgreSQL 8.1November 2010
> PostgreSQL 8.2December 2011
> PostgreSQL 8.3February 2
After a great deal of discussion in the community, the project's core
team have written a policy outlining the support lifecycle for major
PostgreSQL releases, which can be found on the wiki with other project
policies at http://wiki.postgresql.org/wiki/Policies.
We hope this document will help ou
