-
Notifications
You must be signed in to change notification settings - Fork 280
Closed
Labels
1.0.0 blockersTo be addressed before 1.0.0 releaseTo be addressed before 1.0.0 release
Milestone
Description
The recently released v0.20.0 was the last release to include the legacy implementation. In preparation for v1.0.0 it is time to actually say farewell to the legacy implementation. Here is a (likely non-exhaustive) list of related tasks:
- Identify and remove legacy code, tests and documentation
- Review and update continued resources as necessary
- README (e.g. 1.0.0 release and legacy deprecation announcements)
- some python-tuf/docs/
- theupdateframework.io
- TUF specification
- 'passing', 'silver' and 'gold' criteria on bestpractices.coreinfrastructure.org
- ...
- Consider renames
ngclient
->client
IMO the namengclient
makes most sense in relation to the "old" client and so will lose its meaning after the old client has gone, at least after a whileapi.metadata
->metadata
IIRC the api directory was a bit of a crutch to develop new code alongside legacy code without mixing them up, which we won't need after removing the legacy code. IMO api should be designated by other means, e.g. on RTD
Metadata
Metadata
Assignees
Labels
1.0.0 blockersTo be addressed before 1.0.0 releaseTo be addressed before 1.0.0 release