-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Fix #10216] Update the release documentation with feedback from the 21.7.0 release. #1616
Conversation
|
The main changes is making it clear that a review for a release candidate should be asked only after the RC is published on PyPI, But maybe we should ask a review before pushing a PR. Also, before starting the release branch, a message can be sent to IRC or mailing list to see if there is any PR for which the release can be delayed with 1 or 2 days... but not longer. Or just a info that as an optional step, the release manager can communicate the intention of a release . Quick link for the review https://twisted--1616.org.readthedocs.build/en/1616/core/development/policy/release-process.html |
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.
broken URL scheme
|
Thanks @graingert for the review. Much appreciated. I am still updating these notes while working on the release. I will send one final review request after the final Twisted 21.7.0 is out. |
…d/twisted into 10216-release-docs-update-2021-07
|
This is ready for a final review. For now, read the docs updates are manual ... I hope it can be fixed in #1629 |
…d/twisted into 10216-release-docs-update-2021-07
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
Scope and purpose
This is a minor release doc update while doing an actual release.
Updated docs at https://twisted--1616.org.readthedocs.build/en/1616/core/development/policy/release-process.html
Contributor Checklist:
tox -e lintto format my patch to meet the Twisted Coding Standard#character).reviewto the keywords field in Trac, and putting a link to this PR in the comment; it shows up in https://twisted.reviews/ now.The first line is automatically generated by GitHub based on PR ID and branch name.
The other lines generated by GitHub should be replaced.