Update release documents #2720
Update release documents #2720
Conversation
dmcgowan
force-pushed
the
update-release-process
branch
from
4f90218
to
6bbdbd2
Compare
releases/README.md
Outdated
| @@ -0,0 +1,46 @@ | |||
| ## Registry Release Checklist | |||
|
|
|||
| 10. Compile release notes detailing features and since the last release. | |||
releases/README.md
Outdated
| In the case of a release candidate, tick the `pre-release` checkbox. Use | ||
| the generate release notes from the release tool | ||
|
|
||
| 70. Update the registry binary in [distribution library image repo](https://github.com/docker/distribution-library-image) by running the update script and opening a pull request. |
| the release template file and tag to generate the release notes for the tag | ||
| and Github release. To create the tag, you will need PGP installed and a PGP | ||
| key which has been added to your Github account. The comment for the tag will | ||
| be the generate release notes, always compare with previous tags to ensure |
|
|
||
| 60. Create a new [release](https://github.com/docker/distribution/releases). | ||
| In the case of a release candidate, tick the `pre-release` checkbox. Use | ||
| the generate release notes from the release tool |
releases/README.md
Outdated
| In the case of a release candidate, tick the `pre-release` checkbox. Use | ||
| the generate release notes from the release tool | ||
|
|
||
| 70. Update the registry binary in [distribution library image repo](https://github.com/docker/distribution-library-image) by running the update script and opening a pull request. |
There was a problem hiding this comment.
This is me not understanding the historical context but this step of building image manually and pushing to another repo seems convoluted. Is it possible to have https://github.com/docker-library/official-images take binary from https://hub.docker.com/r/distribution/registry/tags/ or just retag with same manifest? Again, this is just for my understanding. Not asking to make any changes.
|
|
||
| `2.3 -> 2.3.1` | ||
|
|
||
| 90. Build a new distribution/registry image on [Docker hub](https://hub.docker.com/u/distribution/dashboard) by adding a new automated build with the new tag and re-building the images. |
There was a problem hiding this comment.
Wouldn't this get built automatically when the tag is pushed in step 50?
| an `-rc` suffix. | ||
| See https://github.com/containerd/containerd/tree/master/cmd/containerd-release | ||
|
|
||
| 20. Update the `.mailmap` files. |
There was a problem hiding this comment.
Is this file generated by the release tool mentioned above? If not then is it created manually? In any case could you mention that explicitly? Something like "Update the .mailmap file manually by looking at authors of commits since last release". I see that you removed AUTHORS target from Makefile. Wasn't that helpful in generating this file?
Remove redundant AUTHORS file in favor of relying on .mailmap for keeping track of author names. Move older changelogs to release directory. Move release checklist to releases README. Signed-off-by: Derek McGowan <[email protected]>
dmcgowan
force-pushed
the
update-release-process
branch
from
6bbdbd2
to
97cb7f3
Compare
Codecov Report
@@ Coverage Diff @@
## master #2720 +/- ##
=======================================
Coverage 60.28% 60.28%
=======================================
Files 103 103
Lines 8003 8003
=======================================
Hits 4825 4825
Misses 2536 2536
Partials 642 642
Continue to review full report at Codecov.
|
Remove redundant AUTHORS file in favor of relying on .mailmap for keeping track of author names.
Move older changelogs to release directory.
Move release checklist to releases README.