Conversation
|
@aniruddha2000: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
ske-prow
bot
added
the
size/M
| - a critical change needs to be rolled out without other major/minor changes | ||
| - it can be promoted automatically | ||
|
|
||
| Both major and minor releases are created from the main branch. Patch releases are created from a release branch that is based on a minor version release. |
There was a problem hiding this comment.
Please describe how the workflow works for creating a patch branch to release a patch version.
There was a problem hiding this comment.
Also add in which cases a patch release is relevant (backport a fix to be able to not release new features with a bug fix)
There was a problem hiding this comment.
is there any existing place where this might be already written?
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
2 participants
How to categorize this PR?
/kind enhancement
/kind documentation
What this PR does / why we need it:
This PR adds documentation for the release process for the machine-controller-manager-provider-stackit. Explaining, major, minor and patch releases and using our release tool.
Special notes for your reviewer:
Breaking changes: