Document VERSION file update scheme
Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com> Upstream-commit: f07ac12791e4af7f199a893705204481588062ae Component: engine
This commit is contained in:
@@ -364,7 +364,17 @@ echo "https://github.com/$GITHUBUSER/docker/compare/docker:master...$GITHUBUSER:
|
||||
Again, get two maintainers to validate, then merge, then push that pretty
|
||||
blue button to delete your branch.
|
||||
|
||||
### 13. Rejoice and Evangelize!
|
||||
### 13. Update the API docs and VERSION files
|
||||
|
||||
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").
|
||||
|
||||
Also create a new entry in `docs/sources/reference/api/` by copying the latest
|
||||
and bumping the version number (in both the file's name and content).
|
||||
|
||||
### 14. Rejoice and Evangelize!
|
||||
|
||||
Congratulations! You're done.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user