| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| Date: | 2020-09-14 15:54:30 |
| Message-ID: | 3c335217-946d-8e90-a7d3-54bb9f37eaf6@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-www |
On 9/14/20 11:25 AM, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Well the question is, does this really apply only to the release notes.
>> What about other changes that are made to the documentation in-between
>> releases?
>> Perhaps we actually want a complete separate docs-load, including back
>> branches, that just gets hidden away somewhere and smacked full of labels
>> that it's not a production set of documentation etc? That would then cover
>> both release notes and reviews of other docs backpatching.
> Yeah, that's quite a plausible proposal.
>
>
Seems fair.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-14 16:35:08 | pgsql: Make walsenders show their replication commands in pg_stat_activ |
| Previous Message | Tom Lane | 2020-09-14 15:25:54 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2020-09-14 16:57:48 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| Previous Message | Tom Lane | 2020-09-14 15:25:54 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |