Greetings,
* Jonathan S. Katz (jkatz@postgresql.org) wrote:
> 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.
Right.
> > 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.
Thanks for working on this Jonathan, but I'm not sure that saying
"Expected Final Release" really changes things. For one thing, having
"Expected Final Release" dates in the past is pretty confusing. For
another, as we've just gone over in some detail, we've agreed to a
release schedule for minor releases and therefore it's sufficient to
just say "Final Release". If we really want to add some words to that,
we could do so above the table.
I'd also change "RELEASE HISTORY" to be something more like "RELEASES"
since it's talking about the future too, not just history.
Thanks!
Stephen
