Re: Unclear EOL

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-18 20:38:37
Message-ID: 263f7ba4-9320-e007-0db9-2d02aab1ee61@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 9/18/18 11:18 AM, Magnus Hagander wrote:
>
> +The PostgreSQL Global Development Group releases a new major version
> containing
> +new features about once a year. Each major version receives bug fixes
> and, if
> +need be, <a href="/support/security/">security</a> fixes that are
> released every three months in what we call a
> +"minor release." For more information on the minor release schedule,
> you can
> +view the <a href="/developer/roadmap/">minor release roadmap</a>.
>
>
> That needs to be "at least every three months". We sometimes release
> more often.
>
>  
>
>
> The one thing that is not included is making "EOL Month" => "Expected
> Last Release" - currently this is set dynamically by
> "core.Version.eoldate"
>
> AFAICT this is only used in one place, on this page, and perhaps we can
> re-purpose it to reflect "Expected Last Release"
>
>
> Yes, that's the only thing it's used for. So you should be able to keep
> using that one, just stop truncating the output to month level in the
> template.

Thanks for the feedback. I have pushed the patch.

Jonathan

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Stephen Frost 2018-09-18 22:08:02 Re: Unclear EOL
Previous Message Magnus Hagander 2018-09-18 15:18:22 Re: Unclear EOL