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

Commit56b4da8

Browse files
committed
Use more modern instructions for creating a new dev cycle
1 parent9994013 commit56b4da8

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

‎src/tools/RELEASE_CHANGES

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,16 +73,20 @@ Starting a New Development Cycle
7373
* Create a branch in git for maintenance of the previous release
7474
o on master branch, do:
7575
git pull # be sure you have the latest "master"
76-
git push origin master:refs/heads/"new-branch-name"
76+
git branch "new-branch-name"
77+
git push -u origin "new-branch-name"
7778
for example,
78-
git push origin master:refs/heads/REL_10_STABLE
79+
git branch REL_11_STABLE
80+
git push -u origin REL_11_STABLE
7981

8082
* Add new branch's name to list in src/tools/git_changelog
8183

8284
* Increment the major version number in src/tools/version_stamp.pl
8385

8486
* Run "src/tools/version_stamp.pl devel", then run autoconf
8587

88+
* Get the buildfarm's 'branches_of_interest.txt' file updated with the new
89+
branch.
8690

8791
Creating Back-Branch Release Notes
8892
==================================

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp