| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Release note trimming: another modest proposal |
| Date: | 2019-02-04 22:23:28 |
| Message-ID: | 25039.1549319008@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
"Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> On 2/4/19 4:25 PM, Tom Lane wrote:
>> After a bit more thought, I'm inclined to propose that the policy be
>> that we *don't* update the surviving back branches for branch retirement.
> ...so I guess in turn, we would not update back branches with newer
> releases as well, i.e. adding references about 12 to 10? That makes
> sense, and eases some of the burden on releases.
No, I definitely didn't have any intention of putting in forward
references to later releases. That seems a bit weird.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2019-02-04 22:35:00 | Re: Release note trimming: another modest proposal |
| Previous Message | Jonathan S. Katz | 2019-02-04 22:13:21 | Re: Release note trimming: another modest proposal |