| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, 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:25:54 |
| Message-ID: | 1033023.1600097154@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-www |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-09-14 15:54:30 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| Previous Message | Magnus Hagander | 2020-09-14 15:16:10 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-09-14 15:54:30 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |
| Previous Message | Magnus Hagander | 2020-09-14 15:16:10 | Re: pgsql: Doc: fill in "major enhancements" list in v13 release notes. |