Skip to content

Version 1.0 release strategy #1645

@joshuagl

Description

@joshuagl

We have a loosely communicated intent to ship python-tuf 1.0 with only the new/refactored code (metadata API + ngclient + ???). We should define what that release looks like, including accounting for:

  • Communicating deprecation expectations with regards the legacy code
    • ADR 2 indicates legacy code will be supported on a best-effort basis, but this has not been communicated to users of python-tuf
    • "Support for older releases: Bugs reported with tuf versions prior to 1.0.0 will likely not be addressed directly by tuf’s maintainers. Pull Requests to fix bugs in the last release prior to 1.0.0 will be considered, and merged (subject to normal review processes). Note that there may be delays due to the lack of developer resources for reviewing such pull requests."

  • What the feature complete state looks like for a python-tuf 1.0 release? Must python-tuf 1.0 provide feature parity with the legacy code?

Metadata

Metadata

Labels

backlogIssues to address with priority for current development goalsdecision recordOutcome of this discussion should be tracked in a decision recorddiscussionDiscussions related to the design, implementation and operation of the project

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions