fcrozat/distribution
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update release checklist with further details

Browse Source 
Add details for release checklist for where to put the update
the changelist and which branch to cherry-pick from. Also add
more details around creating the tag and verifying the tag is
correct.

Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
This commit is contained in:
Derek McGowan 2017-01-18 11:07:35 -08:00
parent 44eff0143e
commit 959659c3fa
No known key found for this signature in database
GPG Key ID: F58C5D0A4405ACDB
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
RELEASE-CHECKLIST.md
View File

@ -1,19 +1,27 @@
## Registry Release Checklist ## Registry Release Checklist
10. Compile release notes detailing features and since the last release. Update the `CHANGELOG.md` file. 10. Compile release notes detailing features and since the last release.
Update the `CHANGELOG.md` file and create a PR to master with the updates.
Once that PR has been approved by maintainers the change may be cherry-picked
to the release branch (new release branches may be forked from this commit).
20. Update the version file: `https://github.com/docker/distribution/blob/master/version/version.go` 20. Update the version file: `https://github.com/docker/distribution/blob/master/version/version.go`
30. Update the `MAINTAINERS` (if necessary), `AUTHORS` and `.mailmap` files. 30. Update the `MAINTAINERS` (if necessary), `AUTHORS` and `.mailmap` files.
``` ```
make AUTHORS make AUTHORS
``` ```
40. Create a signed tag. 40. Create a signed tag.
Distribution uses semantic versioning. Tags are of the format `vx.y.z[-rcn]` Distribution uses semantic versioning. Tags are of the format
You will need PGP installed and a PGP key which has been added to your Github account. The comment for the tag should include the release notes. `vx.y.z[-rcn]`. You will need PGP installed and a PGP key which has been added
to your Github account. The comment for the tag should include the release
notes, use previous tags as a guide for formatting consistently. Run
`git tag -s vx.y.z[-rcn]` to create tag and `git -v vx.y.z[-rcn]` to verify tag,
check comment and correct commit hash.
50. Push the signed tag 50. Push the signed tag