-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 docs: add pre-release actions to release guide #373
📖 docs: add pre-release actions to release guide #373
Conversation
b7fca9a
to
a969bc7
Compare
a969bc7
to
905bac2
Compare
My proposal is to have it documented for now and think about a potential automation in parallel. I updated the docs to reflect that E2E must be updated, as suggested by @furkatgofurov7 |
Thanks @furkatgofurov7 for suggesting we follow a similar release procedure to the one in upstream CAPI https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#prepare-main-branch-for-development-of-the-new-release. I'll update the docs and align the actions with this workflow. |
490392e
to
597bd2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@salasberryfin let's fix some small notes and re-run e2e tests on this one, once you are back 😉
@salasberryfin would you have time to update this PR soon? |
Thanks for the reminder @furkatgofurov7. I forgot that this was still open. |
597bd2a
to
1157e42
Compare
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
1157e42
to
66b5af9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
What this PR does / why we need it:
Add a post-release actions section to release guide.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist: