theupdateframework / theupdateframework/python-tuf
Implement TAP 14
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 304
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
Description
Description of issue or feature request:
Implement TAP 14: Managing TUF versions
Current behavior:
TUF clients will not be able to safely update once the repository moves to a new major specification version.
Expected behavior:
TAP 14 is implemented, giving clients a period of time in which to update to the new specification version
Contributor guide
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 linked TAP 14 specification and comparing its version-management requirements with python-tuf's current behavior. Identify the relevant implementation and test entry points, then define completion as clients safely handling a repository transition to a new major specification version with the stated update period.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100