theupdateframework / theupdateframework/specification
Clarify when local copies of metadata should be loaded in order to support rollback checks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
Rollback checks in the specification imply that previously downloaded locally cached copies of non-root metadata are loaded in order to compare against. However, the specification does not explicitly state that they should be loaded nor provide recommendations on when to load.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the specification sections describing rollback checks and locally cached non-root metadata. Clarify whether and when previously downloaded copies must be loaded, including recommendations for loading; the work is done when the specification removes this ambiguity.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100