Skip to content

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Nov 5, 2025

Comment on lines +71 to +72
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
Copy link
Member Author

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.

Comment on lines -207 to -208
changes to the branch. After the final release is published, the full
:ref:`development cycle <stages>` starts again for the next minor version.
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant