Add step to update website after a release#1218
Add step to update website after a release#1218AkihiroSuda merged 1 commit intoopencontainers:mainfrom
Conversation
Signed-off-by: Brandon Mitchell <git@bmitch.net>
sudo-bmitch
requested review from
AkihiroSuda,
crosbymichael,
cyphar,
dqminh,
giuseppe,
hqhq,
kolyshkin,
mrunalp,
thaJeztah,
tianon,
utam0k and
vbatts
as code owners
| * [ ] attach these docs to the release on <https://github.com/opencontainers/runtime-spec/releases> | ||
| * [ ] 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> |
There was a problem hiding this comment.
The IP stuff seems complicated https://github.com/opencontainers/opencontainers.org/blob/main/content/release-notices/v1-0-2-runtime-spec.md , not sure if this should be written by spec maintainers
There was a problem hiding this comment.
Most of it looks like a copy/paste from previous releases. @amye may know more about what maintainers should handle vs LF.
There was a problem hiding this comment.
The process I've been following for this is to open a draft PR, and then ping our LF contacts who send out the IPR notice and let us know when the 30 day time has expired. I set myself a reminder and merge it then. An example of that I did for runtime-spec is at opencontainers/opencontainers.org#165
LF should also let us know if the member list in our PR needs to be updated. I copy that list from the last merged release notice (from any spec, not only the runtime-spec).
5 participants
Hi runtime-spec maintainers. Apparently none of us have been updating the website's releases page in a while. This adds a step to our release process to fix that. There's some minor markdown cleanup in here too since linters don't like bare URLs or email addresses.