pgsql: Update RELEASE_CHANGES' example of branch name format.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Update RELEASE_CHANGES' example of branch name format.
Date: 2017-08-07 03:26:34
Message-ID: E1deYgc-0007Yt-31@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Update RELEASE_CHANGES' example of branch name format.

We're planning to put an underscore before the major version number in
branch names for v10 and later. Make sure the recipe in RELEASE_CHANGES
reflects that.

In passing, add a reminder to consider doing pgindent right before
the branch.

Discussion: https://postgr.es/m/E1dAkjZ-0003MG-0U@gemulon.postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/655727d93bbaf2569281eea07e38b1955bb627b7

Modified Files
--------------
src/tools/RELEASE_CHANGES | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Ashutosh Sharma 2017-08-07 12:33:32 Re: pgsql: hash: Immediately after a bucket split, try to clean the old buc
Previous Message Peter Geoghegan 2017-08-07 00:40:15 Re: pgsql: Add support for ICU 4.2