Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
0907143f
Commit
0907143f
authored
Mar 31, 2015
by
Zach Loafman
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #6172 from eparis/merge-release-to-master
Instructions to back-merge release branches into master
parents
fc8ba8d7
e9d2c49f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
28 additions
and
2 deletions
+28
-2
mark-new-version.sh
build/mark-new-version.sh
+28
-2
No files found.
build/mark-new-version.sh
View file @
0907143f
...
...
@@ -122,11 +122,37 @@ echo " or find someone who can help solve the tag problem!"
echo
""
if
[[
"
${
VERSION_PATCH
}
"
==
"0"
]]
;
then
echo
"- S
ubmit
branch:
${
current_branch
}
as a PR to master"
echo
"- S
end
branch:
${
current_branch
}
as a PR to master"
echo
"- Get someone to review and merge that PR"
echo
"- Push the new release branch"
echo
" git push git@github.com:GoogleCloudPlatform/kubernetes.git
${
current_branch
}
:
${
release_branch
}
"
else
echo
"- S
ubmit
branch:
${
current_branch
}
as a PR to
${
release_branch
}
"
echo
"- S
end
branch:
${
current_branch
}
as a PR to
${
release_branch
}
"
echo
"- Get someone to review and merge that PR"
echo
""
echo
"Now you need to back merge the release branch into master. This should"
echo
"only be done if you are committing to the latest release branch. If the"
echo
"latest release branch is, for example, release-0.10 and you are adding"
echo
"a commit to release-0.9, you may skip the remaining instructions"
echo
""
echo
"We do this back merge so that master will always show the latest version."
echo
"The version in master would, for exampe show v0.10.2+ instead of v0.10.0+"
echo
"It is not enough to just edit the version file in pkg/version/base.go in a"
echo
"seperate PR. Doing it this way means that git will see the tag you just"
echo
"pushed as an ancestor of master, even though the tag is on on a release"
echo
"branch. The tag will thus be found by tools like git describe"
echo
""
echo
"- Update so you see that merge in origin"
echo
" git remote update"
echo
"- Create and check out a new branch based on master"
echo
" git checkout -b merge-
${
release_branch
}
-to-master origin/master"
echo
"- Merge the
${
release_branch
}
into your merge-
${
release_branch
}
-to-master branch"
echo
" git merge
${
release_branch
}
"
echo
" - It's possible you have merge conflicts."
echo
" - You will almost always want to take what is in HEAD"
echo
" - If you are not SURE how to solve these correctly, ask for help."
echo
" - It is possible to break other people's work if you didn't understand why"
echo
" the conflict happened and the correct way to solve it."
echo
"- Send merge-
${
release_branch
}
-to-master as a PR to master"
echo
"- Take the afternoon off"
fi
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment