Remove TAP 3 + 4 adherence claim #93
Merged
Conversation
This file contains 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
The specification claims that it adheres to TAP 3 and TAP 4, which is not the case. TAP 3 requires changes to the existing metadata format (prepared in theupdateframework#57) and TAP 4 adds a new metadata file (map.json), which is not yet mentioned in the specification (issue described in theupdateframework#88). As agreed in the TUF community meeting on Dec 10, 2019, we remove TAP 3 and TAP 4 (adherence claims), for a formal 1.0.0 release and add TAP 4 in version 1.1.x and TAP 3 in version 2.x.x. (see meeting notes about "Versioning" https://groups.google.com/forum/#!msg/theupdateframework/oPTliXibT_4/0tJ_POLGAwAJ)
joshuagl
previously approved these changes
Mar 3, 2020
|
I assume we will change the "Last modified" date before formally publishing spec version 1.0.0? |
mnm678
previously approved these changes
Mar 3, 2020
trishankatdatadog
previously approved these changes
Mar 3, 2020
lukpueh
dismissed stale reviews from trishankatdatadog, mnm678, and joshuagl
via
5a3ee77
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 specification claims that it adheres to TAP 3 and TAP 4, which is not the case. TAP 3 requires changes to the existing metadata format (prepared in #57) and TAP 4 adds a new metadata file (map.json), which is not yet mentioned in the specification (issue described in #88).
As agreed in the TUF community meeting on Dec 10, 2019, we remove TAP 3 and TAP 4 (adherence claims) for a formal 1.0.0 release and will add TAP 4 in version 1.1.x and TAP 3 in version 2.x.x.
(see meeting notes about "Versioning" )
NOTE: Let's ignore the version management strategy and checker results for this PR. As agreed in the meeting (see notes above) this will be the last change before we formally release TUF 1.0.0. After that, we should stick to the rules defined in #87.