Re: pgsql: Improve draft release notes. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Improve draft release notes.
Date
Msg-id 10039.1386007498@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Improve draft release notes.  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-committers
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


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: doc: update wording of ineffective SET and ABORT commands
Next
From: Tom Lane
Date:
Subject: pgsql: Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19.