Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork931
Clarify development cycle#1681
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| There is usually either one or two maintenance branches at any given time. | ||
| After the final release of a new minor version (3.x.0), releases |
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.
It's always Python 3.x, we don't care about 2.x any more.
If there's a 4.x, and things change, we'll update it then.
| changes to the branch. After the final release is published, the full | ||
| :ref:`development cycle<stages>` starts again for the next minor version. |
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.
Incorrect.
After the final release is published in October, the dev cycle for the next one had already started back in May.
Uh oh!
There was an error while loading.Please reload this page.
📚 Documentation preview 📚:https://cpython-devguide--1681.org.readthedocs.build/