| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Unclear EOL |
| Date: | 2018-09-06 02:54:46 |
| Message-ID: | 2448.1536202486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
David Fetter <david(at)fetter(dot)org> writes:
> That's an excellent point. I'm thinking we could supply only the dates
> in the past and, only when we know it, one date in the future, so
> something like:
> Version Current minor Supported First release date EOL month Last release date
> 10 10.5 Yes October 2017 October 2022 N/A
> 9.6 9.6.10 Yes September 2016 September 2021 N/A
> 9.5 9.5.14 Yes January 2016 January 2021 N/A
> 9.4 9.4.19 Yes December 2014 December 2019 N/A
> 9.3 9.3.24 Yes September 2013 September 2018 November 8, 2018 (tentative)
> 9.2 9.2.24 No September 2012 September 2017 November 9, 2017
> ...
What exactly is the point of that?
I think the main effect it would have is to encourage people to think
they'll continue to have support past the stated EOL month. That seems
counterproductive for all concerned.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-09-06 14:15:15 | Re: Unclear EOL |
| Previous Message | David Fetter | 2018-09-05 23:45:14 | Re: Unclear EOL |