TrueCloudLab/distribution
13
0
Fork 3
Code Issues 3 Pull requests Projects Releases 2 Packages Wiki Activity Actions
distribution/releases
History
Milos Gajdos c72db4109c
Prep for v3-beta1 release 
Created a changelog file
Updated mailmap
Updated version

Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com>
2024-07-09 19:31:16 +01:00
..
README.md Cleanup of naming in docs 2023-10-12 11:39:36 +01:00
v2.5.0-changelog.txt Update release documents 2018-09-26 18:30:44 -07:00
v2.6.0-changelog.txt Update release documents 2018-09-26 18:30:44 -07:00
v2.7.0.toml go.mod: change imports to github.com/distribution/distribution/v3 2021-02-08 18:30:46 +01:00
v3.0.0-alpha.1.toml Prep for v3-beta1 release 2024-07-09 19:31:16 +01:00
v3.0.0-beta.1.toml Prep for v3-beta1 release 2024-07-09 19:31:16 +01:00

README.md

Registry Release Checklist

  1. Compile release notes detailing features added since the last release.

Add release template file to releases/ directory. The template is defined by containerd's release tool. Name the file using the version, for rc add an -rc suffix. See https://github.com/containerd/release-tool

  1. Update the .mailmap files.

  2. Update the version file: https://github.com/distribution/distribution/blob/master/version/version.go

  3. Create a signed tag.

Choose a tag for the next release, distribution uses semantic versioning and expects tags to be formatted as vx.y.z[-rc.n]. Run the release tool using 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 generated release notes, always compare with previous tags to ensure the output is expected and consistent. Run git tag --cleanup=whitespace -s vx.y.z[-rc.n] -F release-notes to create tag and git -v vx.y.z[-rc.n] to verify tag, check comment and correct commit hash.

  1. Push the signed tag

  2. Create a new release. In the case of a release candidate, tick the pre-release checkbox. Use the generate release notes from the release tool

  3. Update the registry binary in the distribution library image repo by running the update script and opening a pull request.

  4. Update the official image. Add the new version in the official images repo by appending a new version to the registry/registry file with the git hash pointed to by the signed tag. Update the major version to point to the latest version and the minor version to point to new patch release if necessary. e.g. to release 2.3.1

2.3.1 (new)

2.3.0 -> 2.3.0 can be removed

2 -> 2.3.1

2.3 -> 2.3.1

  1. Build a new distribution/registry image on Docker Hub by adding a new automated build with the new tag and re-building the images.