-
Notifications
You must be signed in to change notification settings - Fork 103
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
Update release.md to better reflect our release process #1112
Conversation
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 for keeping RELEASE.md
up-to-date! This look great, just got some smaller corrections.
RELEASE.md
Outdated
1. The release issue is closed | ||
1. Every release should have an appointed release manager (RM) | ||
1. RM is responsible for following the process below | ||
1. RM should announce the release in the public kubernetes channel at least two days prior to the date |
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.
Could you detail this a bit, I'm not sure which public channel is meant here. And this is about Slack or a mailing list?
Co-Authored-By: Jan Schlicht <jan@d2iq.com>
Co-Authored-By: Jan Schlicht <jan@d2iq.com>
@nfnt updated :) |
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.
LGTM!
No description provided.