| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Unclear EOL |
| Date: | 2018-09-11 14:08:47 |
| Message-ID: | 1f9ac478-ce13-8c0a-a074-9b75e9535cee@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 09/09/2018 18:01, Tom Lane wrote:
>> As for a specific suggestion, I would amend our current policy to state
>> that we support each major version for 5 years, with the last release of
>> a given major version being the planned minor release following the 5
>> year mark.
>
> Seems reasonable to me. Maybe s/planned/scheduled/ for clarity.
So that would mean that if the EOL month is September and the next minor
release is scheduled for November, but we do an unplanned release in
October, we would then have to still support it until November? Or if
we skip the November release, we have to keep going until February?
I think a bit of ambiguity is good here. After the EOL month, you're on
your own. We might do something afterwards for technical or bookkeeping
reasons or because we think it's important, but don't count on it.
Maybe in five years we'll be releasing a minor every three weeks, how do
we adjust the policy then? Let's not over-specify this.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-09-11 14:15:02 | Re: Unclear EOL |
| Previous Message | Marčela Mioč | 2018-09-11 13:57:08 | Request for "editor" privileges |