Document image revision tags - #5
Merged
Merged
Conversation
Replace the obsolete stability-tag description with version-line and exact-version image revisions. Explain compatibility, product-version exceptions, and the shared image revision policy.
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
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.
The README still described image tags as semantic stability tags. Replace that guidance with the current image revision format, including version-line and full-version counters, matching Git tags, and development variants.
Explain that revision numbers do not indicate compatibility, retain previously published tags, and link to the image revision policy. Backup product versions and third-party tag formats remain distinct.
Validation: reviewed the Markdown and policy link, confirmed the image-tag section is the only change, and checked that the obsolete terminology is gone.