From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Release note trimming: another modest proposal |
Date: | 2018-08-30 20:15:19 |
Message-ID: | CABUevEzX3dq-uUeMR0mSnCj4B6TK3v4QuQKKsf6Oz+ZdyRHMZg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Aug 10, 2018 at 1:38 AM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 06/08/2018 00:57, Tom Lane wrote:
> > Anyway, I'd like to propose a compromise position that I don't think
> > has been discussed before: let's drop release notes for branches
> > that were already EOL when a given branch was released. So for
> > example, 9.3 and before would go away from v12, due out next year.
> > Working backwards, we'd drop 9.1 and before from v10, giving the 15%
> > savings in page count that I showed above. A quick measurement says
> > that would also trim the size of the v10 tarball by about 4%, which
> > is not a lot maybe but it's noticeable across a lot of downloads.
>
> Why not go further and just ship the release notes of the current major
> version. If you want to look at the release notes of version 11, read
> the documentation for version 11. Who reads the documentation of
> version 12 to get the release notes of version 11?
>
+1 for that. At least if we get a generic release notes index up on the
website, easy to find.
That might also make the process of manually merging release notes back and
forth in the release process easier, I assume?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2018-08-30 20:19:28 | Re: Release note trimming: another modest proposal |
Previous Message | Magnus Hagander | 2018-08-30 20:13:22 | Re: Release note trimming: another modest proposal |