From: Tom Lane Date: Mon, 7 Aug 2017 03:26:09 +0000 (-0400) Subject: Update RELEASE_CHANGES' example of branch name format. X-Git-Tag: REL_10_BETA3~13 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=655727d93bbaf2569281eea07e38b1955bb627b7;p=postgresql.git 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 --- diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index dc1b300a352..b7963c2449c 100644 --- a/src/tools/RELEASE_CHANGES +++ b/src/tools/RELEASE_CHANGES @@ -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