From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Release note trimming: another modest proposal |
Date: | 2019-02-05 14:12:56 |
Message-ID: | 18071.1549375976@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> For the record: I think this is a terrible idea. Makes it much harder to
> figure out what changed when, and requires per-branch incantations to
> grep through the log.
Uh ... "grep through the log"? The git log output hasn't changed at all.
I've personally never found the SGML/HTML release notes to be even
slightly useful for search purposes, because they're spread across so
many files. This just changes how many copies of those files we have.
> That's not to speak of the fact that now it's
> just about impossible to reference all releasenotes on the website in a
> useful manner now.
You can still point to, say,
https://www.postgresql.org/docs/devel/release.html
There's maybe two more clicks needed to reach any particular back
branch from there, but I would not call that "just about impossible".
Anyway, if people want something resembling the old presentation,
I think the way to get there is to have some sort of aggregate
release notes in a separate place on the web site. We'd discussed
that briefly upthread, but no one's volunteered to push it through.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2019-02-05 14:17:40 | Re: Release note trimming: another modest proposal |
Previous Message | Jonathan S. Katz | 2019-02-05 13:50:16 | Re: Release note trimming: another modest proposal |