Re: Maintenance Policy? - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Maintenance Policy?
Date
Msg-id 4A59361B.6060002@agliodbs.com
Whole thread Raw
In response to Re: Maintenance Policy?  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Responses Re: Maintenance Policy?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Hmmm, how about this?

"The current policy of the PostgreSQL community is to stop providing 
minor versions (patches or updates) of PostgreSQL five years after a 
version of PostgreSQL is released.  In general, users can expect to 
continue to be able to get community updates for five years.

However, there have been exceptions in both directions.  Some companies 
choose to continue back-patching PostgreSQL and make those updates 
available to the community past the fifth anniversary.  Other times 
issues with build tools have caused us to discontinue a particular 
version early, such as 8.0 and 8.1 for Windows, which stopped getting 
updates in binary form after only 2 years.

Overall, if you have specific lifetime requirements for your database 
products, we strongly urge you to get a long-term support contract with 
a PostgreSQL support vendor <link>.

As examples of this policy, below are the dates at which updates of 
specific version became unavailable:

<table here>
"

-- 
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: concurrent index builds unneeded lock?
Next
From: Andrew Dunstan
Date:
Subject: Re: Maintenance Policy?