| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Unclear EOL |
| Date: | 2018-09-05 22:02:45 |
| Message-ID: | 4c187f85-8276-3655-225b-f47f77778e89@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 09/05/2018 02:57 PM, Adrian Klaver wrote:
> On 09/05/2018 02:37 PM, David Fetter wrote:
>> Folks,
>>
>> The EOLs listed in the table aren't super specific looking forward.
>>
>> https://www.postgresql.org/support/versioning/
>>
>> Would it be OK to name the (planned) release date of the final minor
>> release in that table?
>>
>> I'm asking because I've had some complaints from people who assume, I
>> believe reasonably, that that table represents the actual EOL and not
>> the current meaning of, "the date past which the date of the next
>> point release is planned to come out."
>
> I am not getting that. If you look at 10:
>
> Version Current minor Supported First release date EOL date
> 10 10.5 Yes October 2017 October 2022
>
> EOL of life is at the 5 years support stated. At that point no further
> releases will be done on it.
Hmm, read David J.'s post and learned something. There is one more minor
release done. Still, I figure that the EOL date(month) is the one I
ought to have upgraded by.
>
>
>>
>> What say?
>>
>> Best,
>> David.
>>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-09-05 22:04:24 | Re: Unclear EOL |
| Previous Message | Adrian Klaver | 2018-09-05 21:57:49 | Re: Unclear EOL |