| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(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-20 00:57:57 |
| Message-ID: | 75a8a197-a9cc-f58a-45b3-47715eac9ea1@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Hi Stephen,
On 9/18/18 6:08 PM, Stephen Frost wrote:
>
> 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 for the suggestions. I have made the changes.
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2018-09-20 03:11:13 | Re: Code of Conduct plan |
| Previous Message | Tatsuo Ishii | 2018-09-19 21:41:06 | Re: Code of Conduct plan,Re: Code of Conduct plan |