On 07Jul2020 0321, Raymond Hettinger wrote:
My two cents: I think this should be a little more liberal. At beta 1, freeze the addition of new features but continue to tweak the implementation with code clean-ups, additional tests, algorithmic improvements, and better docs.
All of those things are allowed during beta, provided the public facing API does not change.
And if you identify a genuine problem, I think you'll find the policy is actually more liberal than you suggest ;) It just requires RM involvement to keep the rate of change under control, rather than letting anyone check in their "essential" improvements at any time.
As for the rest of your suggestions, I agree, but "we" had the release cycle discussion last year and decided that making the next major release come up sooner (12 months instead of 18) was the best way to solve those concerns.
Cheers, Steve _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/IFOATZ7M7CSB7EWQNJ7D4E4ZRAKWY6XN/ Code of Conduct: https://www.python.org/psf/codeofconduct/
