kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Merge pull request #15065 from calavera/new_release_branch_workflow

Browse source 
Make the release process more atomic between major releases.
This commit is contained in:
David Calavera 2015-08-13 16:10:11 -07:00
commit 54b50479af
1 changed files with 35 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
project/RELEASE-CHECKLIST.md
View file

@ -24,22 +24,49 @@ git remote add $GITHUBUSER git@github.com:$GITHUBUSER/docker.git
### 1. Pull from master and create a release branch ### 1. Pull from master and create a release branch
Note: Even for major releases, all of X, Y and Z in vX.Y.Z must be specified (e.g. v1.0.0). All releases version numbers will be of the form: vX.Y.Z where X is the major
version number, Y is the minor version number and Z is the patch release version number.
#### Major releases
The release branch name is just vX.Y because it's going to be the basis for all .Z releases.
```bash ```bash
export BASE=vX.Y
export VERSION=vX.Y.Z export VERSION=vX.Y.Z
git fetch origin git fetch origin
git branch -D release || true git checkout --track origin/master
git checkout --track origin/release git checkout -b release/$BASE
```
This new branch is going to be the base for the release. We need to push it to origin so we
can track the cherry-picked changes and the version bump:
```bash
git push origin release/$BASE
```
When you have the major release branch in origin, we need to create the bump fork branch
that we'll push to our fork:
```bash
git checkout -b bump_$VERSION git checkout -b bump_$VERSION
``` ```
If it's a regular release, we usually merge master. #### Patch releases
If we have the release branch in origin, we can create the forked bump branch from it directly:
```bash ```bash
git merge origin/master export VERSION=vX.Y.Z
export PATCH=vX.Y.Z+1
git fetch origin
git checkout --track origin/release/$BASE
git checkout -b bump_$PATCH
``` ```
Otherwise, if it is a hotfix release, we cherry-pick only the commits we want. We cherry-pick only the commits we want into the bump branch:
```bash ```bash
# get the commits ids we want to cherry-pick # get the commits ids we want to cherry-pick
git log git log
@ -169,7 +196,7 @@ make AWS_S3_BUCKET=beta-docs.docker.io BUILD_ROOT=yes docs-release
git add VERSION CHANGELOG.md git add VERSION CHANGELOG.md
git commit -m "Bump version to $VERSION" git commit -m "Bump version to $VERSION"
git push $GITHUBUSER bump_$VERSION git push $GITHUBUSER bump_$VERSION
echo "https://github.com/$GITHUBUSER/docker/compare/docker:release...$GITHUBUSER:bump_$VERSION?expand=1" echo "https://github.com/$GITHUBUSER/docker/compare/docker:release/$BASE...$GITHUBUSER:bump_$VERSION?expand=1"
``` ```
That last command will give you the proper link to visit to ensure that you That last command will give you the proper link to visit to ensure that you
@ -185,6 +212,7 @@ Replace "..." with the respective credentials:
```bash ```bash
docker build -t docker . docker build -t docker .
docker run \ docker run \
-e AWS_S3_BUCKET=test.docker.com \ -e AWS_S3_BUCKET=test.docker.com \
-e AWS_ACCESS_KEY="..." \ -e AWS_ACCESS_KEY="..." \