| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | 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-11 14:39:55 |
| Message-ID: | 20180911143955.GJ4184@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Greetings,
* Jonathan S. Katz (jkatz(at)postgresql(dot)org) wrote:
> I think we are saying similar things though...the content of the page
> needs some hierarchical restructuring, and yes, I'm convinced of some
> language cleanups as well.
>
> To make it more tangible, I'm happy to propose a patch in a few.
The point I was getting at is that we don't just need a patch here- our
current EOL policy is really quite vague and confusing. Trying to
reword that confusing and vague policy doesn't change that it's
confusing and vague- to deal with that, we need to actually change the
policy, which is what I'm advocating for here.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-09-11 14:52:52 | Re: Unclear EOL |
| Previous Message | Jonathan S. Katz | 2018-09-11 14:37:48 | Re: Unclear EOL |