This is a friendly reminder from the release management team that the first release candidate of Python 3.10 is next Monday. Now is a fantastic time you make sure that:
## If you are a user or library developer
3.10, check that the bug is properly fixed.
type system, it works with the new additions in 3.10 https://docs.python.org/3.10/whatsnew/3.10.html#summary-release-highlights .
application/library with Python 3.10
## If you are a core developer or a member of the triage team
https://docs.python.org/3.10/whatsnew/3.10.html (if you have doubts, you can ask me ;) ).
Some technical details of the release candidate:
Once the 3.10 branch reaches RC status, it only can have bug fixes applied that have been reviewed by other core developers (so you cannot merge your own PR without review even if you are a core dev). Generally, these issues must be severe enough (e.g. crashes) that they deserve fixing before the final release. All other issues should be deferred to the next development cycle (Python 3.10.1) since stability is the strongest concern at this point. Also bear in mind that once we reach the RC, the *ABI is frozen* and cannot change even for bug fixes.
While the goal is to have no code changes between an RC and a final release, there may be a need for final documentation o test fixes. Any such proposed changes should be discussed first with the release manager.
*You cannot skip the peer review during an RC*, no matter how small! Even if it is a simple copy-and-paste change, everything requires peer review from a core developer.
(You can find these instructions and details in the devguide https://devguide.python.org/devcycle/#rc).
Thank you all for your help!
Regards from rainy London, Pablo Galindo Salgado