Introduce semantic versioning 2.0.0 and disambiguates spec versions#51
Merged
JustinCappos merged 6 commits intomasterfrom Sep 17, 2019
Merged
Introduce semantic versioning 2.0.0 and disambiguates spec versions#51JustinCappos merged 6 commits intomasterfrom
JustinCappos merged 6 commits intomasterfrom
Conversation
added 3 commits
September 13, 2019 16:22
Move tuf-spec.0.9.txt to subdir to avoid confusion with current specification working document, i.e. tuf-spec.md.
- Changes "1.0" to "1.0.0" and bumps the "Last modified" date in the specification working document. NOTE: the "(Draft)" supplement is not part of semantic versioning - Mentions use of semantic versioning in the spec's readme
Member
JustinCappos
left a comment
There was a problem hiding this comment.
Do we need the "Draft" tag for version 1.0.0? Otherwise it looks good to merge.
Member
JustinCappos
left a comment
There was a problem hiding this comment.
Do we also want to update the TAPs to say what version they are included in? (If not, I'm fine merging this as-is.)
Merged
3 tasks
Member
Author
I'd only remove it if this revision is the final 1.0.0 version of the specification. In that case we should also tag it as such. Does anyone, more familiar with the specification, want to make the call? @JustinCappos, @mnm678, @SantiagoTorres, @trishankatdatadog? |
c90c69d to
5e063a7
Compare
JustinCappos
approved these changes
Sep 17, 2019
Member
JustinCappos
left a comment
There was a problem hiding this comment.
Removing draft tag from spec.
lukpueh
pushed a commit
to lukpueh/specification
that referenced
this pull request
Oct 17, 2019
theupdateframework#51 updates the format of the "spec_version" field in any tuf metadata to strictly require a string that conforms to the Semantic Versioning 2.0.0 standard. This commit updates the metadata examples in the specification accordingly.
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
4 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.
Closes #36 and #33
SPEC_VERSIONfield in TUF metadata must be a string that follows semantic versioning.tuf-spec.0.9.txttohistorical/tuf-spec.0.9.txtto avoid confusion with current specification working document, i.e.tuf-spec.md, which currently is a draft for 1.0.0.