From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Maintenance Policy? |
Date: | 2009-07-11 00:16:47 |
Message-ID: | E21F5637-7783-4FAB-ACED-5D2E9A98E2BA@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 10, 2009, at 6:01 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> All,
>
> I'd suggest that we publish an official policy, with the following
> dates for "EOL":
>
> 7.4 2009-08-01
> 8.0 2010-02-01
> 8.1 2011-01-01
> 8.2 2012-01-01
> 8.3 2013-03-01
> 8.4 2014-08-01
>
> EOL would be defined as:
>
> "After the above dates, the PostgreSQL Project will not promise to
> provide any minor (patch or update) releases of the respective
> versions, whether for security, data loss, or any other issue.
> Individual companies might choose to continue backporting patches to
> earlier versions, and if they contribute these update releases we
> will make them available. However, after the final minor release
> date, there is no guarantee that updates will be available and users
> should upgrade."
It seems pretty speculative to propose end of support dates for every
active release at this point; what if it takes us longer than planned
to get the next few releases out?
I think we could try to set dates for the older releases.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-07-11 00:29:33 | Re: Maintenance Policy? |
Previous Message | Bruce Momjian | 2009-07-10 23:52:14 | Re: Maintenance Policy? |