diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-06 23:26:09 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-06 23:26:09 -0400 |
| commit | 655727d93bbaf2569281eea07e38b1955bb627b7 (patch) | |
| tree | e258b7a9bcf9a751185555bcc0d9075d3ceb7b77 | |
| parent | b35006ecccf505d05fd77ce0c820943996ad7ee9 (diff) | |
| download | postgresql-655727d93bbaf2569281eea07e38b1955bb627b7.tar.gz postgresql-655727d93bbaf2569281eea07e38b1955bb627b7.zip | |
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
| -rw-r--r-- | src/tools/RELEASE_CHANGES | 4 |
1 files changed, 3 insertions, 1 deletions
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 |