What the developer wrote
Authored by Tim Ruffing
release-process: Add "cleaning up"
What changed, and why it matters
This commit simply adds a short 'Cleaning up' section to the project's release-process documentation. It describes administrative tasks like closing a GitHub milestone and removing a label after a release. There is no code change and no security relevance.
No security action needed; this is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies doc/release-process.md only, appending two post-release housekeeping steps: closing the GitHub milestone and removing the ‘needs-changelog’ label from merged PRs. No source code, build scripts, cryptographic logic, or configuration is changed.
Changed components
doc/release-process.mdInspect captured patch +6 / −0
diff --git a/doc/release-process.md b/doc/release-process.md
index 9bbcd68..bc224ce 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -108,3 +108,9 @@ Note that bug fixes need to be backported only to releases for which no compatib
2. Create a new GitHub release with a link to the corresponding entry in [CHANGELOG.md](../CHANGELOG.md).
Attach the tarball and the detached signature.
3. Send an announcement email to the bitcoin-dev mailing list.
+
+
+## Cleaning up
+
+1. Close the GitHub milestone, and create a new one. Consider moving unresolved issues to the new milestone.
+2. Remove the `needs-changelog` label from all merged PRs.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.