On 23 November 2016 at 06:40, Steve Dower <steve.do...@python.org> wrote: > On 22Nov2016 1150, R. David Murray wrote: >> >> Being who we are (precisionist programmers), the inconsistency between >> "beta release cuts off features" and "last beta before RC cuts off >> non-release-critical fixes" does produce some cognitive dissonance. >> I've seen the RC described as "the first beta that might be turned into >> the production release", and if you think of it that way it makes it >> easier to remember that we're restricting commits in order to produce that >> "special beta". That is probably better, conceptually, than producing >> an RC that we fully expect will require release-critical bug fixes because >> we just committed a bunch of non-release-critical bug fixes, just >> so cutoff-when-the-name-changes stays consistent. > > > It might also help if the version info was updated to (for example) > "3.6.0rc1-" rather than "3.6.0b4+", to emphasize that any work going on in > that branch is work against RC and not against a beta. > > I'm not sure that a trailing '-' is the right way to mark this. Maybe > "rc1+dev" or similar?
The "3.6.0rc0+" notation would reflect that it's not a beta any more, but still comes before rc1. (While Donald's right that PEP 440 recommends a ".dev0" suffix for this use case, we don't allow for that in the interpreter level version reporting APIs, while an "rc0" suffix should work fine) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
