doc: remove recommendation to wait a week for point release.
What the developer wrote
Authored by Rusty Russell
doc: remove recommendation to wait a week for point release.
With more developers, inevitably there are PRs queued during the
release process. Just accept that there will need to be a branch
created for any point release.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
What changed, and why it matters
This commit simply edits an internal project document (the release checklist) to remove a suggestion that developers wait one week after a release before deciding whether a point release is needed. It is purely a process/documentation change and has no effect on the software's code, behavior, or security.
No security action needed. This is a normal documentation/process update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change modifies doc/contribute-to-core-lightning/release-checklist.md, renumbering the post-release checklist items after deleting the ‘Wait for a week to see if we need any point releases!’ step. No source code, build scripts, tests, or configuration files are touched.
Changed components
doc/contribute-to-core-lightning/release-checklist.mdInspect captured patch +4 / −5
diff --git a/doc/contribute-to-core-lightning/release-checklist.md b/doc/contribute-to-core-lightning/release-checklist.md
index 29da107d..bbf8b126 100644
--- a/doc/contribute-to-core-lightning/release-checklist.md
+++ b/doc/contribute-to-core-lightning/release-checklist.md
@@ -97,11 +97,10 @@ Here's a checklist for the release process.
## Post-release
-1. Wait for a week to see if we need any point releases!
-2. Create a PR to update Makefile's CLN_NEXT_VERSION and important dates for the next release on `.github/PULL_REQUEST_TEMPLATE.md`.
-3. Look through PRs which were delayed for release and merge them.
-4. Close out the Milestone for the now-shipped release.
-5. Update this file with any missing or changed instructions.
+1. Create a PR to update Makefile's CLN_NEXT_VERSION and important dates for the next release on `.github/PULL_REQUEST_TEMPLATE.md`.
+2. Look through PRs which were delayed for release and merge them.
+3. Close out the Milestone for the now-shipped release.
+4. Update this file with any missing or changed instructions.
## Performing the Point (hotfix) Release
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.