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

Add a few more small RELEASE-CHECKLIST tweaks, fixes, and improvements

Browse source
This commit is contained in:
Tianon Gravi 2013-11-22 11:39:40 -07:00
parent 58f8503b73
commit 37e0083169
1 changed files with 20 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
hack/RELEASE-CHECKLIST.md
View file

@ -5,7 +5,6 @@ So you're in charge of a Docker release? Cool. Here's what to do.
If your experience deviates from this document, please document the changes If your experience deviates from this document, please document the changes
to keep it up-to-date. to keep it up-to-date.
### 1. Pull from master and create a release branch ### 1. Pull from master and create a release branch
```bash ```bash
@ -13,7 +12,7 @@ export VERSION=vXXX
git checkout release git checkout release
git pull git pull
git checkout -b bump_$VERSION git checkout -b bump_$VERSION
git merge master git merge origin/master
``` ```
### 2. Update CHANGELOG.md ### 2. Update CHANGELOG.md
@ -55,10 +54,14 @@ EXAMPLES:
### 3. Change the contents of the VERSION file ### 3. Change the contents of the VERSION file
```bash
echo ${VERSION#v} > VERSION
```
### 4. Run all tests ### 4. Run all tests
```bash ```bash
docker run -privileged -lxc-conf=lxc.aa_profile=unconfined docker hack/make.sh test docker run -privileged docker hack/make.sh test
``` ```
### 5. Test the docs ### 5. Test the docs
@ -80,8 +83,8 @@ git push origin bump_$VERSION
### 8. Apply tag ### 8. Apply tag
```bash ```bash
git tag -a $VERSION git tag -a $VERSION -m $VERSION bump_$VERSION
git push --tags git push origin $VERSION
``` ```
Merging the pull request to the release branch will automatically Merging the pull request to the release branch will automatically
@ -92,6 +95,9 @@ documentation releases, see ``docs/README.md``
### 9. Go to github to merge the bump_$VERSION into release ### 9. Go to github to merge the bump_$VERSION into release
Don't forget to push that pretty blue button to delete the leftover
branch afterwards!
### 10. Publish binaries ### 10. Publish binaries
To run this you will need access to the release credentials. To run this you will need access to the release credentials.
@ -108,17 +114,19 @@ docker run \
-e AWS_ACCESS_KEY=$(cat ~/.aws/access_key) \ -e AWS_ACCESS_KEY=$(cat ~/.aws/access_key) \
-e AWS_SECRET_KEY=$(cat ~/.aws/secret_key) \ -e AWS_SECRET_KEY=$(cat ~/.aws/secret_key) \
-e GPG_PASSPHRASE=supersecretsesame \ -e GPG_PASSPHRASE=supersecretsesame \
-privileged -lxc-conf=lxc.aa_profile=unconfined \ -i -t -privileged \
-t -i \
docker \ docker \
hack/release.sh hack/release.sh
``` ```
It will build and upload the binaries on the specified bucket (you should It will run the test suite one more time, build the binaries and packages,
use test.docker.io for general testing, and once everything is fine, and upload to the specified bucket (you should use test.docker.io for
switch to get.docker.io). general testing, and once everything is fine, switch to get.docker.io).
### 11. Rejoice and Evangelize!
### 11. Rejoice!
Congratulations! You're done. Congratulations! You're done.
Go forth and announce the glad tidings of the new release in `#docker`,
`#docker-dev`, on the [mailing list](https://groups.google.com/forum/#!forum/docker-dev),
and on Twitter!