| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Release note trimming: another modest proposal |
| Date: | 2018-08-09 23:45:08 |
| Message-ID: | 4817.1533858308@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> 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.
> 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?
Personally, I'd be OK with that, but it seemed to me that that had
already been proposed and shot down (on the grounds of not-enough-
history) the last time this was discussed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-08-10 01:01:31 | Re: Release note trimming: another modest proposal |
| Previous Message | Peter Eisentraut | 2018-08-09 23:38:43 | Release note trimming: another modest proposal |