docs: Update release documentation to address pain points #4626
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
Original pain points identified: 1. Clarify label back porting flow 2. Fix broken documentation release 3. Fix :latest docker tag issue (1) and (2) are addressed by this change. (3) has been captured in an issue: grafana/pyroscope-squad#645.
Contributor
Author
|
I was originally going to propose a release candidate process, but I decided the work involved in migrating our automation adds more risk than the incremental process gain is worth. This documentation update addresses the pain points sufficiently. |
simonswine
approved these changes
Nov 20, 2025
Contributor
simonswine
left a comment
simonswine
left a comment
There was a problem hiding this comment.
Thanks for updating, that all makes sense to me
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Original pain points identified:
(1) and (2) are addressed by this change. (3) has been captured in an issue: https://github.com/grafana/pyroscope-squad/issues/645.