docs(dev): add Step 0 to release process runbook#589
Open
Conversation
Captures the convention introduced in the 0.6.1 cycle: before preparing the changelog or branching, open a GitHub issue to coordinate the release, explain why we are cutting it now, and list any unusual pre-release todos. Routine steps are already covered by this runbook and need not be repeated.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #589 +/- ##
=======================================
Coverage 73.67% 73.67%
=======================================
Files 22 22
Lines 4483 4483
=======================================
Hits 3303 3303
Misses 1180 1180 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds Step 0 to
doc/dev/release-process.md: open a release issue before preparing the changelog or branching.Captures the convention introduced in the 0.6.1 cycle (see #588). The issue should explain why we are cutting the release now, summarize what is in it (including any motivation or backstory), and list unusual pre-release todos. Routine steps are already covered by the runbook.