| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, 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-01-25 23:46:14 |
| Message-ID: | 20190125234614.GH13803@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Jan 25, 2019 at 06:41:20PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I assume this means we would only keep the current release notes in the
> > git tree too, e.g. 11.0, 11.1, 11.2, etc.
>
> Yeah, I'd imagine that each branch would have just its own release notes.
>
> I'm not sure whether to apply this policy retroactively to the supported
> back branches or just establish it going forward. Maintaining the notes
> could be pretty confusing for the next few years if we do the latter,
> though.
Agreed. We would need to backpatch.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2019-01-26 01:32:12 | Re: First SVG graphic |
| Previous Message | Tom Lane | 2019-01-25 23:41:20 | Re: Release note trimming: another modest proposal |