database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-07 00:36:50 +03:00
Code Activity

Update RELEASE_CHANGES' example of branch name format.

Browse Source 
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
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/tools/RELEASE_CHANGES
View File

@ -68,12 +68,14 @@ For Major Releases
Starting a New Development Cycle 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 * Create a branch in git for maintenance of the previous release
o on master branch, do: o on master branch, do:
git pull # be sure you have the latest "master" git pull # be sure you have the latest "master"
git push origin master:refs/heads/"new-branch-name" git push origin master:refs/heads/"new-branch-name"
for example, 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 * Add new branch's name to list in src/tools/git_changelog