Skip to content

Remove "legacy code" #1745

@lukpueh

Description

@lukpueh

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
  • Consider renames
    • ngclient -> client
      IMO the name ngclient 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 while
    • api.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 release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions