-
Notifications
You must be signed in to change notification settings - Fork 3.8k
chore: update RELEASE.md with instructions #6519
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
chore: update RELEASE.md with instructions #6519
Conversation
b119f79
to
25f66be
Compare
bf7f443
to
15e8735
Compare
| v0.67 | 2023-07-26 | Simon Pasquier (GitHub: @simonpasquier) | | ||
| v0.66 | 2023-06-14 | Arthur Sens (Github: @ArthurSens) | | ||
| v0.65 | 2023-05-03 | Philip Gough (GitHub: @PhilipGough) | | ||
|
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.
@simonpasquier removed old entries as per suggestion
15e8735
to
b42e3cc
Compare
@simonpasquier addressed comments |
@simonpasquier @slashpai Can I apply as a release volunteer for v0.75? |
release is done by maintainers :) |
Signed-off-by: Jayapriya Pai <[email protected]>
b42e3cc
to
987d04c
Compare
Can I apply to become a member of maintainers? :) |
Description
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Improved release docs
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
x
in the box that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.