docs(release-docs): add note regarding cherry picking branch
### What does this PR do?
Adds a small note that you must fix create the branch by specifying the
tag in the step, before continuing.
### 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, found during release process.
### How to test this PR?
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
We have kind/* labels for task, release, and technical debt, but our templates don't
cover any of these - you have to create a feature or a bug and then change the type.
This takes longer and leaves a bunch of odd fields in the issue, e.g. 'Is your
feature request related to a problem?'
We're switching to use Github issue types which also includes these three types.
It should be easier to create one of these issue types, but we also don't want to
clutter up the template list with lots of 'internal' types that will make it more
confusing to external users. The proposal is just to add Task, which is generic
enough and easier to switch to Technical debt or Release.
Part of #14777.
Signed-off-by: Tim deBoer <git@tdeboer.ca>
### What does this PR do?
We usually have it non-capitalized (only capitalize first letter) for
our blogs, release notes, etc. But our templates have every letter
capitalized.
### 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). -->
References: https://github.com/containers/podman-desktop/pull/9628#discussion_r1824469966
### 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 <charlie@charliedrage.com>
* 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
<!-- 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 <charlie@charliedrage.com>
* update based on review
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
---------
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
add example of command line I used that is matching the
release notes format to display PR being fixed
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
The 'playing' attribute sets the player to auto-start, but it is starting
full screen. Adding 'playsinline' to every react player should ensure that
it doesn't go full screen on phones.
Fixes#6335.
Signed-off-by: Tim deBoer <git@tdeboer.ca>
* docs: release schedule
### What does this PR do?
Adds what we usually do as a release schedule
### Screenshot/screencast of this PR
<!-- Please include a screenshot or a screencast
explaining what is doing this PR -->
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?
N/A
<!-- Please explain steps to reproduce -->
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* docs: add part about staging
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
---------
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
avoid to promote directly releases being rolling out
it introduces an extra step to verify the release
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
* docs: update release note docs
### What does this PR do?
* Updates the release note docs with minor changes encountered as a result of doing another release.
* Adds a template for blog posting.
### Screenshot/screencast of this PR
<!-- Please include a screenshot or a screencast explaining what is doing this PR -->
N/A
### What issues does this PR fix or reference?
<!-- Please include any related issue from Podman Desktop repository (or from another issue tracker).
-->
N/A
### How to test this PR?
<!-- Please explain steps to reproduce -->
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* docs: update based on review
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
---------
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
### What does this PR do?
Updates the release documentation with more notes / explanations when I
was going through the release.
### Screenshot/screencast of this PR
<!-- Please include a screenshot or a screencast explaining what is doing this PR -->
N/A
### What issues does this PR fix or reference?
<!-- Please include any related issue from Podman Desktop repository (or from another issue tracker).
-->
N/A
### How to test this PR?
N/A
<!-- Please explain steps to reproduce -->
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
