opencontainers/distribution-spec
1
0
Fork 0
mirror of https://github.com/opencontainers/distribution-spec.git synced 2025-04-18 20:04:03 +03:00
Code

Add a release step for specs.opencontainers.org

Browse Source 
Signed-off-by: Brandon Mitchell <git@bmitch.net>
This commit is contained in:
Brandon Mitchell 2025-01-24 10:52:01 -05:00
parent eeddb23523
commit e032387939
No known key found for this signature in database
GPG Key ID: 6E0FF28C767A8BEE
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
RELEASES.md
View File

@ -64,7 +64,7 @@ Releases usually follow a few steps:
- [ ] a commit bumping `./specs-go/version.go` to next version and empty the `VersionDev` variable
- [ ] a commit adding back the "+dev" to `VersionDev`
- [ ] send email to <dev@opencontainers.org>
- [ ] copy the exact commit hash for bumping the version from the pull-request (since master always stays as "-dev")
- [ ] copy the exact commit hash for bumping the version from the pull-request (since master always stays as "+dev")
- [ ] count the PRs since last release (that this version is tracking, in the cases of multiple branching), like `git log --pretty=oneline --no-merges --decorate $priorTag..$versionBumpCommit | grep \(pr\/ | wc -l`
- [ ] get the date for a week from now, like `TZ=UTC date --date='next week'`
- [ ] OPTIONAL find a cute animal gif to attach to the email, and subsequently the release description
@ -95,5 +95,6 @@ $sig
- [ ] link to the the VOTE thread and include the passing vote count
- [ ] link to the pull request that merged the release
- [ ] add release notes to the website <https://github.com/opencontainers/opencontainers.org/tree/main/content/release-notices>
- [ ] update the version number at <https://github.com/opencontainers/specs.opencontainers.org> in `_data/specs.yaml`
[charter]: https://github.com/opencontainers/tob/blob/main/CHARTER.md