Thread: pgsql: Improve draft release notes.
Improve draft release notes. Per suggestions from Andres Freund. Also fix spelling of Sergey Burladyan's name. Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/b8b7b723f29e39769486545aef61d71edcadff80 Modified Files -------------- doc/src/sgml/release-9.3.sgml | 75 ++++++++++++++++++++++++++++------------- 1 file changed, 52 insertions(+), 23 deletions(-)
>On 2 December 2013 17:17, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Improve draft release notes. > > Per suggestions from Andres Freund. Also fix spelling of > Sergey Burladyan's name. > > Branch > ------ > master > > Details > ------- > http://git.postgresql.org/pg/commitdiff/b8b7b723f29e39769486545aef61d71edcadff80 > > Modified Files > -------------- > doc/src/sgml/release-9.3.sgml | 75 ++++++++++++++++++++++++++++------------- > 1 file changed, 52 insertions(+), 23 deletions(-) Hi Tom, What does this text mean in the SGML? +<!-- +Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> +Branch: master [4c697d8f4] 2013-11-18 09:51:09 +0200 +Branch: REL9_3_STABLE [ea2bb1b47] 2013-11-18 10:16:31 +0200 +Branch: REL9_2_STABLE [3379263b6] 2013-11-18 10:12:22 +0200 +--> -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Simon Riggs <simon@2ndQuadrant.com> writes:
> What does this text mean in the SGML?
> +<!--
> +Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
> +Branch: master [4c697d8f4] 2013-11-18 09:51:09 +0200
> +Branch: REL9_3_STABLE [ea2bb1b47] 2013-11-18 10:16:31 +0200
> +Branch: REL9_2_STABLE [3379263b6] 2013-11-18 10:12:22 +0200
> +-->
That's chunks of the git_changelog output I was working from. I use it
as a guide to know which changelog items should go into which back
branches. I'll strip the comments after I've finished making all the
back-branch notes, but this is just a working copy at the moment.
regards, tom lane
On 2013-12-02 12:44:56 -0500, Tom Lane wrote: > Simon Riggs <simon@2ndQuadrant.com> writes: > > What does this text mean in the SGML? > > > +<!-- > > +Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> > > +Branch: master [4c697d8f4] 2013-11-18 09:51:09 +0200 > > +Branch: REL9_3_STABLE [ea2bb1b47] 2013-11-18 10:16:31 +0200 > > +Branch: REL9_2_STABLE [3379263b6] 2013-11-18 10:12:22 +0200 > > +--> > > That's chunks of the git_changelog output I was working from. I use it > as a guide to know which changelog items should go into which back > branches. I'll strip the comments after I've finished making all the > back-branch notes, but this is just a working copy at the moment. FWIW I vote for leaving them in, even though it admittedly only helps the few people looking at the sgml, it is quite useful information. I wish it always had been in there. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-12-02 12:44:56 -0500, Tom Lane wrote:
>> That's chunks of the git_changelog output I was working from. I use it
>> as a guide to know which changelog items should go into which back
>> branches. I'll strip the comments after I've finished making all the
>> back-branch notes, but this is just a working copy at the moment.
> FWIW I vote for leaving them in, even though it admittedly only helps
> the few people looking at the sgml, it is quite useful information. I
> wish it always had been in there.
Meh. In cases where multiple commits have been summarized into one
bullet point, that wouldn't work too well. I guess we could keep *all*
of the relevant commit items in the comment, but I didn't do so this
time; I only worried about being sure the correct set of back branches
appeared in each comment.
I'm willing to start doing it that way in future if enough people
like the idea, but I don't want to go back and figure out what to
add to the lists in this set.
regards, tom lane