Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit655727d

Browse files
committed
Update RELEASE_CHANGES' example of branch name format.
We're planning to put an underscore before the major version number inbranch names for v10 and later. Make sure the recipe in RELEASE_CHANGESreflects that.In passing, add a reminder to consider doing pgindent right beforethe branch.Discussion:https://postgr.es/m/E1dAkjZ-0003MG-0U@gemulon.postgresql.org
1 parentb35006e commit655727d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎src/tools/RELEASE_CHANGES

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,12 +68,14 @@ For Major Releases
6868
Starting a New Development Cycle
6969
================================
7070

71+
* Typically, we do pgindent and perltidy runs just before branching
72+
7173
* Create a branch in git for maintenance of the previous release
7274
o on master branch, do:
7375
git pull # be sure you have the latest "master"
7476
git push origin master:refs/heads/"new-branch-name"
7577
for example,
76-
git push origin master:refs/heads/REL9_2_STABLE
78+
git push origin master:refs/heads/REL_10_STABLE
7779

7880
* Add new branch's name to list in src/tools/git_changelog
7981

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp