docs: correct RELEASING.md — issues not enforced (missed #113's merge) - #114
Merged
Conversation
Per the decision to keep process light: release notes generate from merged PRs, so a good PR title is the whole requirement. The earlier draft prescribed an issue-per-work / `Closes #N` discipline "to adopt next cycle" -- that is now explicitly NOT enforced, so the doc is corrected to match rather than left carrying a standing commitment the project has declined. Labels are documented as optional grouping only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
This commit was pushed to
feat/release-notesas #113 was merging, so it missed the merge. Main still carries the RELEASING.md section that prescribes an issue-per-work /Closes #Ndiscipline — which was explicitly declined.Corrects the doc to match the decision: release notes come from PRs, issues and commit-linking are not enforced, labels are optional grouping only. No code change.
Flagged rather than buried because it is exactly the "a doc carrying a standing commitment the project declined" failure mode noted earlier — a KB/doc that disagrees with reality is worse than one that is merely thin.
1258 tests pass (doc-only).
🤖 Generated with Claude Code