Re: Maintenance Policy?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Page <dpage(at)pgadmin(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maintenance Policy?
Date: 2009-07-07 17:18:45
Message-ID: 20090707171844.GH7694@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David E. Wheeler wrote:
> On Jul 7, 2009, at 9:13 AM, Andrew Dunstan wrote:
>
>> One thing I think we really should do is give prominent public notice
>> of any EOL for a branch. At least a couple of months, preferably. If
>> the lifetime were absolutely fixed it might not matter so much, but as
>> it isn't I think we owe that to our users.
>
> Perhaps a maintenance page on the site with a table for each version of
> PostgreSQL, in reverse chronological order, showing the initial release
> date and the date of last supported release (anticipated, perhaps, to be
> something like Sept 1 for 7.4).

We have an RSS:
http://www.postgresql.org/versions.rss

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-07 17:22:28 Re: WIP: generalized index constraints
Previous Message Greg Stark 2009-07-07 17:18:06 Re: Synch Rep: direct transfer of WAL file from the primary to the standby