Re: pgsql: Adjust Release Notes to reflect holding off wrapped expanded mod

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Adjust Release Notes to reflect holding off wrapped expanded mod
Date: 2014-08-18 23:19:42
Message-ID: 12382.1408403982@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Greg Stark <stark(at)mit(dot)edu> writes:
> On Mon, Aug 18, 2014 at 4:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Actually, that needs to be done in master, which is always the
>> authoritative copy of release-note SGML files.

> hm, interesting. ok.

To clarify --- there's certainly no harm in patching the back-branch
copies too. But when Bruce or I work on the release notes, what we
generally do is work on the master-branch copies, and then copy those
files verbatim into the relevant back branches. The reason for the
file-per-branch structure of the release notes is to make this easy.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2014-08-19 03:10:10 pgsql: Install libpq DLL with $(INSTALL_SHLIB).
Previous Message Greg Stark 2014-08-18 22:13:07 pgsql: Adjust Release Notes to reflect holding off wrapped expanded mod