Skip to content

docs: move release facts to the release reference - #12

Merged
showxu merged 1 commit into
masterfrom
docs/release-reference
Oct 22, 2026
Merged

showxu merged 1 commit into
masterfrom
docs/release-reference

Conversation

@showxu

@showxu showxu commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Follows the organization's document roles: version rules live only in VERSIONING, and a repository's release facts and procedure live in its release reference.

  • Documentation/Architecture/VersioningAndRelease.md is retired. Its rules that the organization VERSIONING.md already states are replaced by links. Its release facts are now in Documentation/Reference/Release.md, organized by the release reference sections:
    • components and version sources;
    • compatibility surface;
    • dependencies and verified combinations;
    • derived metadata and drift checks;
    • candidate, acceptance and publication;
    • evidence reuse and invalidation;
    • entry points and artifact retention.
  • The repository has no version rule that differs from the organization's, so it keeps no root VERSIONING.md.
  • Every inbound link and index entry is updated.

Documentation only.

Validation

  • Local link and anchor checks, packaged manual checks, and a search for the retired path.
  • The repository's Python tests and its deterministic package build.

@showxu
showxu force-pushed the docs/release-reference branch from ef34121 to 3300574 Compare October 22, 2026 05:04
@showxu
showxu merged commit 2e7658a into master Oct 22, 2026
6 checks passed
@showxu
showxu deleted the docs/release-reference branch October 22, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant