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 #20010 from thaJeztah/update-release-checklist

Browse source 
Release checklist - bump versions earlier
This commit is contained in:
David Calavera 2016-02-04 18:07:06 -08:00
commit 98aa1d24a3
1 changed files with 18 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
project/RELEASE-CHECKLIST.md
View file

@ -76,15 +76,25 @@ git cherry-pick <commit-id>
... ...
``` ```
### 2. Bump the API version on master ### 2. Update the VERSION files and API version on master
We don't want to stop contributions to master just because we are releasing. At We don't want to stop contributions to master just because we are releasing.
the same time, now that the release branch exists, we don't want API changes to So, after the release branch is up, we bump the VERSION and API version to mark
go to the now frozen API version. the start of the "next" release.
Create a new entry in `docs/reference/api/` by copying the latest and #### 2.1 Update the VERSION files
bumping the version number (in both the file's name and content), and submit
this in a PR against master. Update the content of the `VERSION` file to be the next minor (incrementing Y)
and add the `-dev` suffix. For example, after the release branch for 1.5.0 is
created, the `VERSION` file gets updated to `1.6.0-dev` (as in "1.6.0 in the
making").
#### 2.2 Update API version on master
We don't want API changes to go to the now frozen API version. Create a new
entry in `docs/reference/api/` by copying the latest and bumping the version
number (in both the file's name and content), and submit this in a PR against
master.
### 3. Update CHANGELOG.md ### 3. Update CHANGELOG.md
@ -490,14 +500,7 @@ echo "https://github.com/$GITHUBUSER/docker/compare/docker:master...$GITHUBUSER:
Again, get two maintainers to validate, then merge, then push that pretty Again, get two maintainers to validate, then merge, then push that pretty
blue button to delete your branch. blue button to delete your branch.
### 24. Update the VERSION files ### 24. Rejoice and Evangelize!
Now that version X.Y.Z is out, time to start working on the next! Update the
content of the `VERSION` file to be the next minor (incrementing Y) and add the
`-dev` suffix. For example, after 1.5.0 release, the `VERSION` file gets
updated to `1.6.0-dev` (as in "1.6.0 in the making").
### 25. Rejoice and Evangelize!
Congratulations! You're done. Congratulations! You're done.