| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Release note trimming: another modest proposal |
| Date: | 2018-08-09 23:38:43 |
| Message-ID: | fa460b8a-e581-ee7c-0118-a89f7b9e1cf9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-09 23:45:08 | Re: Release note trimming: another modest proposal |
| Previous Message | Vik Fearing | 2018-08-09 21:35:56 | Re: Typo in doc or wrong EXCLUDE implementation |