-
Notifications
You must be signed in to change notification settings - Fork 389
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
[release-0.20] 📖 update release process doc #3010
[release-0.20] 📖 update release process doc #3010
Conversation
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
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.
/approve
LGTM label has been added. Git tree hash: b030cb735b38db533d9099ab2c3ec64386dc3a13
|
/retest |
1 similar comment
/retest |
/approve |
1 similar comment
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mjudeikis, sttts, xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/retest c'mon! |
Summary
I would like to cherry-pick #2988 for two reasons:
release-*
branch is first created. A push event to the branch would be necessary, which we could achieve with a simple cherry-pick PR like this one being merged.Therefore I would like to merge at least one commit to
release-0.20
, so we get documentation deployed to docs.kcp.io. it might not be strictly necessary and the docs are probably outdated, but I think it would be nice to have the version at least available on docs.kcp.io, now that people are perhaps curious what project is going to join the CNCF here.Related issue(s)
Fixes #
Release Notes