Skip to content
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

Describe how updates should occur on the repository side #105

Closed
joshuagl opened this issue Jul 6, 2020 · 3 comments
Closed

Describe how updates should occur on the repository side #105

joshuagl opened this issue Jul 6, 2020 · 3 comments

Comments

@joshuagl
Copy link
Member

joshuagl commented Jul 6, 2020

the spec does not have a notion of developer uploads. As a matter of fact, and I think this should be changed, right now it does not even describe how updates occur on the repository-side (as we do in PEP-458).

Originally posted by @lukpueh in #104 (comment)
@joshuagl
Copy link
Member Author

joshuagl commented Jul 7, 2020

Related issue in the reference implementation theupdateframework/python-tuf#969

@JustinCappos JustinCappos mentioned this issue Jul 9, 2020
Merged
joshuagl added a commit to joshuagl/specification that referenced this issue Oct 6, 2020
@joshuagl
Add repository metadata generation sequence
2a6eb6e 
Fixes: theupdateframework#105

Signed-off-by: Joshua Lock <[email protected]>
joshuagl added a commit to joshuagl/specification that referenced this issue Oct 6, 2020
@joshuagl
Add repository metadata generation sequence
b2ea1ac 
Specify in which order metadata should be generated and made available on
the repository.

Fixes: theupdateframework#105

Signed-off-by: Joshua Lock <[email protected]>
@joshuagl joshuagl mentioned this issue Oct 6, 2020
Closed
@joshuagl
Copy link
Member Author

joshuagl commented Oct 6, 2020

I've opened a PR #126 to include the recommended metadata write order, as detailed in PEP 458.

I think it makes sense to include more detailed workflows/recommendations in the proposed secondary literature (#91).

joshuagl added a commit to joshuagl/specification that referenced this issue Oct 6, 2020
@joshuagl
Add repository metadata generation sequence
4f9eca5 
Specify in which order metadata should be generated and made available on
the repository.

Fixes: theupdateframework#105

Signed-off-by: Joshua Lock <[email protected]>
joshuagl added a commit to joshuagl/specification that referenced this issue Oct 6, 2020
@joshuagl
Add repository metadata generation sequence
92f5cbc 
Specify in which order metadata should be generated and made available on
the repository.

Fixes: theupdateframework#105

Signed-off-by: Joshua Lock <[email protected]>
joshuagl added a commit to joshuagl/specification that referenced this issue Oct 6, 2020
@joshuagl
Add repository metadata generation sequence
d2bc296 
Specify in which order metadata should be generated and made available on
the repository.

Fixes: theupdateframework#105

Signed-off-by: Joshua Lock <[email protected]>
@joshuagl joshuagl mentioned this issue Mar 29, 2021
Merged
@joshuagl
Copy link
Member Author

Resolved by #153

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Specify in which order metadata should be published to the repository joshuagl/specification
1 participant
@joshuagl