Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add step to update website after a release #1107

Merged
merged 1 commit into from
Nov 15, 2023

Conversation

sudo-bmitch
Copy link
Contributor

We need to be sure to update the website after we push releases. This adds the step to our release process.

Signed-off-by: Brandon Mitchell <git@bmitch.net>
Copy link
Member

@tianon tianon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can see, @caniszczyk is currently maintaining those; I'm going to give him a chance to confirm it would be helpful for us to be doing this explicitly before merging. 👍

@caniszczyk
Copy link
Contributor

I generally do it but having it part of the process where someone can send a PR here is nice! https://github.com/opencontainers/opencontainers.org/

The big thing I need to watch is the release notices on the website for major versions as those are required to be published per OCI IP rules and I have to send a separate note to OCI members when that happens

@tianon tianon merged commit 56fb783 into opencontainers:main Nov 15, 2023
@sudo-bmitch sudo-bmitch deleted the pr-release-notice branch November 15, 2023 22:18
@sudo-bmitch sudo-bmitch mentioned this pull request Jan 11, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants