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
This commit is contained in:
Tom Lane 2017-08-06 23:26:09 -04:00
parent b35006eccc
commit 655727d93b

View File

@ -68,12 +68,14 @@ For Major Releases
Starting a New Development Cycle
================================
* Typically, we do pgindent and perltidy runs just before branching
* Create a branch in git for maintenance of the previous release
o on master branch, do:
git pull # be sure you have the latest "master"
git push origin master:refs/heads/"new-branch-name"
for example,
git push origin master:refs/heads/REL9_2_STABLE
git push origin master:refs/heads/REL_10_STABLE
* Add new branch's name to list in src/tools/git_changelog