chore: update release procedure #1945
Draft
+21
−29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think I was the first person to try the release procedure, and there were a few things that were out of date or clearly copied from Podman Desktop. - There is no label kind/release (and I don't think it's worth creating one). - Simplified to 'maintainers', since it's not necessarily the same set of people. - The release timeline was just copied from Podman Desktop and completely wrong this time - at least clarified that's when we're releasing at the same time. - Improved ordering of / simplified closing the release vs issues in it. - Version bump PR is not auto-merged, changed the wording. - Clarified it's the catalog that actually makes the release visible. - Moved checking the published image to the correct place in the workflow (before we test it). - Simplified/reorganized/reformatted the testing and publishing sections. - Minor wording improvements. Related to containers#1842. Signed-off-by: Tim deBoer <[email protected]>
deboer-tim
requested review from
benoitf,
jeffmaury and
a team
as code owners
axel7083
approved these changes
Oct 17, 2024
jeffmaury
requested changes
Oct 18, 2024
|
|
||
| ## Next phase | ||
| - Create a branch if it does not exist. For example 1.2.1 if 1.2.0 failed. Then, cherry-pick bugfixes into that branch. |
There was a problem hiding this comment.
We use 1.2.x on Podman Desktop see https://github.com/containers/podman-desktop/blob/56e136426096a6685f6fb5fb509ba2bd2cb2f916/RELEASE.md?plain=1#L54
|
setting as draft as there were no updates since one month |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
I think I was the first person to try the release procedure, and there were a few things that were out of date or clearly copied from Podman Desktop.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
Related to #1842.
How to test this PR?
N/A