-
Notifications
You must be signed in to change notification settings - Fork 165
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 0.16 release #1370
Prepare 0.16 release #1370
Conversation
I want to pull the trigger and exclude some PRs like #1349 because I feel we have accumulated enough changes to have a release. Our last release was in the end of June 2024, so I think it is time. For the remaining changes that are out I think they can wait for a 0.16.1 or 0.17 release. Lastly, generally this is a PR with many typo fixes but we should be much better after #1330. I'd focus on checking all new methods are documented. |
Pull Request Test Coverage Report for Build 12940015874Details
💛 - 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.
LGTM, if you think we're ready to release I think we're good to go. Just some small notes on the prelude.
Co-authored-by: Matthew Treinish <[email protected]>
@mtreinish I will tag the release tonight and monitor the wheel builds. Thanks for the swift review! |
This commit prepares the 0.16.0 release. It moves the release notes for the release into a separate directory and adds a prelude to the release notes. This should be the last commit to merge for the 0.16.0 release and after it merges that commit will be what is should be tagged as the 0.16.0 release.