Re: Maintenance Policy?

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).

So something like:
 branch |  released  | curr_version | curr_date  | final_date
--------+------------+--------------+------------+------------ 8.4    | 2009-07-01 | 8.4.0        | 2009-07-01 | 8.3
|2008-02-04 | 8.3.7        | 2009-03-16 | 8.2    | 2006-12-05 | 8.2.13       | 2009-03-16 | 8.1    | 2005-11-08 |
8.1.17      | 2009-03-16 | 8.0    | 2005-01-19 | 8.0.21       | 2009-03-16 | 7.4    | 2003-11-17 | 7.4.25       |
2009-03-16| 2009-09-01  
 
(projected) 7.3    | 2002-11-27 | 7.3.21       | 2008-01-07 | 2008-01-07 7.2    | 2002-02-04 | 7.2.8        |
2005-05-09| 2005-05-09 7.1    | 2001-04-13 | 7.1.3        | 2001-08-15 | 2001-08-15 7.0    | 2000-05-08 | 7.0.3
|2000-11-11 | 2000-11-11
 

Best,

David