Skip to content

Reference the map file in the specification (TAP4) #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
vladimir-v-diaz opened this issue May 24, 2017 · 5 comments
Open

Reference the map file in the specification (TAP4) #88

vladimir-v-diaz opened this issue May 24, 2017 · 5 comments
Assignees
@joshuagl
Milestone
1.1.0

Comments

@vladimir-v-diaz
Copy link
Contributor

TAP 4 (the map file) describes how users may specify that a certain repository should be used for some targets, while other repositories are to be used for other targets.

We should reference the map file in the specification once TAP 4 is reviewed and accepted, which depends on the acceptance of TAP 7 (conformance testing). Pending pull request for the map file implementation is available here: theupdateframework/python-tuf#430

A detailed outline of the map file should be covered in the specification, similar to pull request theupdateframework/python-tuf#440 that has now been merged.
@joshuagl
Copy link
Member

The specification is now in a separate repository theupdateframework/specification, should this issue be moved there?

@lukpueh lukpueh transferred this issue from theupdateframework/python-tuf Feb 5, 2020
@lukpueh lukpueh changed the title Reference the map file in the specification Reference the map file in the specification (TAP4) Feb 5, 2020
lukpueh added a commit to lukpueh/specification that referenced this issue Mar 3, 2020
@lukpueh
Remove TAP 3 + 4 adherence claim
37bfe61 
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)
@lukpueh lukpueh mentioned this issue Mar 3, 2020
Merged
@lukpueh
Copy link
Member

lukpueh commented Mar 3, 2020

As discussed in the TUF community meeting on Dec 10, 2019 the changes of this PR require a minor bump of the spec version (see meeting notes about "Versioning" ).

@joshuagl
Copy link
Member

joshuagl commented Jun 1, 2020

I'm planning to take a stab at this over the next week or two.

@joshuagl
Copy link
Member

For the interested, I submitted theupdateframework/taps#117 to try and clean up TAP 4 before I work on this.

@joshuagl
Copy link
Member

I haven't forgotten this work, but I want to discuss and resolve #109 on documenting concepts first.

@joshuagl joshuagl self-assigned this Oct 6, 2020
@mnm678 mnm678 added this to the 1.1.0 milestone Apr 29, 2021
@mnm678 mnm678 mentioned this issue Apr 29, 2021
Closed
@rdimitrov rdimitrov mentioned this issue Apr 6, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joshuagl joshuagl

Labels
None yet
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
4 participants
@lukpueh @vladimir-v-diaz @mnm678 @joshuagl