-
Notifications
You must be signed in to change notification settings - Fork 277
Prepare v0.20.0 #1723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare v0.20.0 #1723
Conversation
This will be the final release of python-tuf that includes the legacy implementation code. Please see the [*1.0.0 announcement*](1.0.0-ANNOUNCEMENT.md) page for more details about the next release and the deprecation of the legacy implementation, including migration instructions. Signed-off-by: Lukas Puehringer <[email protected]>
Pull Request Test Coverage Report for Build 1572875550
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Metadata API: Remove dependency on dateutil #1722 looks like a blocker
- announcement link is wrong (see below)
otherwise LGTM
legacy implementation code. Please see the [*1.0.0 | ||
announcement*](1.0.0-ANNOUNCEMENT.md) page for more details about the next |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if that was a mistake but the 1.0.0 announcement ended up in root dir so this link does not work. Do we move the announcement?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦 Thanks for catching this!
I've got an updated branch in https://github.com/jku/python-tuf/tree/release-0.20.0 but
|
Cool, thanks! Do you want to merge the README change with this PR, or create a separate one? Also, while changing the README, would you mind adding the cncf python-tuf slack channel to the contact section? I'm pointing migration help seekers to that section in the 1.0.0-ANNOUNCEMENT doc, and I think the slack channel would be a good way to reach out to us.
I am not so concerned about minor breaking changes prior to 1.0.0. But yeah, ...
... the rename can easily land with 0.20 (just merged). |
I can make a new PR, thanks |
NOTE: This will be the final release of python-tuf that includes the legacy implementation code. Please see the 1.0.0 announcement page for more details about the next release and the deprecation of the legacy implementation, including migration instructions.
Added
Advertize type annotations with py.typed #1677, Tests on the new implementation: address mypy warnings #1687, Move linters configurations in pyproject.toml #1699, Start linting the examples folder #1701, Lint additional four files in the tests folder #1708, Start linting the test #1710, test: add missing return type hint in test method #1720)
Changed
Removed