Require the first version to read only "Initial release." - #27
Merged
Merged
Conversation
Add the rule to doc/POLICY.md, for both a module's own Version History and doc/VERSIONS: the entry at the lowest version reads only "Initial release." and nothing else. Apply it to every genuine v1.0 module entry currently carrying other wording. doc/VERSIONS' own v1.0 is a modernization release, not the project's genuine first version (no earlier release tag or version file exists), so its record is left as the substantial multi-line entry it is; the added policy text notes this explicitly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TrTUHxoev25aExf2UTAnHM
3 tasks
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
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.
Summary
Replaces the earlier #26 (closed without merging): that PR incorrectly collapsed
doc/VERSIONS'v1.0entry to "Initial release.", butv1.0here is a modernization release — no earlier release tag or version file exists, so it is not the project's genuine first version and its substantial multi-line record is restored as-is.doc/POLICY.md, for both a module's ownVersion Historyanddoc/VERSIONS: an entry at the lowest genuine first version reads onlyInitial release.and nothing else.v1.0per-module header entry (23 files) currently carrying other wording.doc/VERSIONS' ownv1.0entry untouched; the added policy text explicitly notes it is a modernization release, not the genuine first version.Test plan
doc/VERSIONSand per-moduleVersion Historysections; 0 bullets exceed two physical lines.py_compile/sh -non every changed file; all pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01TrTUHxoev25aExf2UTAnHM
Generated by Claude Code