add RELEASE.md document #143
Merged
+53
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FranzBusch
reviewed
Sep 16, 2025
Co-authored-by: Franz Busch <[email protected]>
incertum
reviewed
Sep 16, 2025
Sources/Prometheus/RELEASE.md
Outdated
|
|
||
| Step 2) Make the GitHub Release and Release Notes. | ||
|
|
||
| Release notes generation is automated and based on the enforced labelling of pull requests. |
There was a problem hiding this comment.
Would it be possible to suggest some ways to make this paragraph more concise or step-by-step instructional?
There was a problem hiding this comment.
I'll revisit today then
Co-authored-by: Melissa Kilby <[email protected]>
Updated instructions for generating release notes on GitHub.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need a release.md if we are to request moving to prom org, so adding a simple one.