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. |
|
[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 |
xoxys
left a comment
There was a problem hiding this comment.
In general, we should follow the document structure from https://github.com/stackitcloud/cloud-provider-stackit/blob/main/docs/release-procedure.md e.g.
| git checkout -b release-vx.y vx.y.0 | ||
| git push -u origin release-vx.y | ||
| ``` | ||
| 3. Use `/cherry-pick release-vx.y` command in the PR with the changes. The ronovate will open the cherry-pick PR automatically. |
There was a problem hiding this comment.
| 3. Use `/cherry-pick release-vx.y` command in the PR with the changes. The ronovate will open the cherry-pick PR automatically. | |
| 3. Use `/cherry-pick release-vx.y` command in the PR with the changes. The prow will open the cherry-pick PR automatically. |
| @@ -1 +1 @@ | |||
| # Release Procedure | |||
There was a problem hiding this comment.
can we keep the same structure of the file as in https://github.com/stackitcloud/cloud-provider-stackit/blob/main/docs/release-procedure.md
Example the Publishing a Release is on the other doc called Automated Release Process (Primary Method. Or Versioning -> General Information
@xoxys added this already as a comment: #136 (review)
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: