docs: update documentation on cherry picking releases #7804
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
cdrage
requested review from
dgolovin and
jeffmaury
and removed request for
a team
cdrage
force-pushed
the
update-cherrypicking-steps
branch
from
dd32aee
to
66766b7
Compare
benoitf
reviewed
Jun 24, 2024
|
|
||
| At this step, generates as well Flathub pull request so people can test the package from the builders of the pull request. | ||
| At this step, it also generates a Flathub pull request so people can test the package from the builders of the pull request. |
There was a problem hiding this comment.
not sure about the 'it' changes in 'it also generates' as it's a person that needs to do that for now
There was a problem hiding this comment.
does it not automatically generate it? or we do it manually?
RELEASE.md
Outdated
| You'll need to create another release from the 1.3.x branch. This can be done by doing the following: | ||
| 1. Go to `Run workflow` in the [release steps](/RELEASE.md#releasing-on-github) again. | ||
| 2. **MAKE SURE** you specify that you want to use the `1.3.x` branch, NOT `main` under `Branch to use for the release`. | ||
| 3. Version to release should be `1.3.x` |
There was a problem hiding this comment.
Suggested change
| 3. Version to release should be `1.3.x` | |
| 3. Version to release should be `1.3.z` (like 1.3.1, 1.3.2, etc.) |
### What does this PR do? Updates our release documentation on how to cherry pick PRs and spin up another release. ### Screenshot / video of UI <!-- If this PR is changing UI, please include screenshots or screencasts showing the difference --> N/A ### What issues does this PR fix or reference? <!-- Include any related issues from Podman Desktop repository (or from another issue tracker). --> N/A ### How to test this PR? <!-- Please explain steps to verify the functionality, do not forget to provide unit/component tests --> N/A Signed-off-by: Charlie Drage <[email protected]>
cdrage
force-pushed
the
update-cherrypicking-steps
branch
from
66766b7
to
b2506d1
Compare
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.
docs: update documentation on cherry picking releases
What does this PR do?
Updates our release documentation on how to cherry pick PRs and spin up
another release.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
N/A
How to test this PR?
N/A
Signed-off-by: Charlie Drage [email protected]