docs(metadata): drop 'same release train' wording from versioning section - #296
Merged
Merged
Conversation
…tion The architecture assumes independent per-package releases, not a coordinated release train. Reword the versioning bump guidance to "coordinate producer/consumer support as needed before shipping the breaking version" and state explicitly that there is no coordinated release train. Closes #295
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
docs/METADATA_SPEC.mdto reflect independent per-package releases rather than a coordinated release train.Notes
agent-playbook.md's "lockstep" refers to tests/docs, not releases — out of scope).docs/METADATA_SPEC.mdhas no translated variants, so no translation sync is required.Closes #295