On 9/30/2019 3:48 AM, Łukasz Langa wrote:
To help our chances, please avoid any source-related activity on the 3.8 branch from now until the release of 3.8.0. Yes, that also counts for bug fixes unless they are critical. (Yeah, it might be a bit annoying but nobody wants to be the person who introduced a last minute regression in a major release.)
In the past, x.y.zrc1 has been tagged and branched somehow so that commits to x.y are commits to x.y.z+, the future x.y.(z+1). (I never paid attention to the details). For instance, 3.7 is currently 3.7.4+. As soon as Ned makes 3.7.5rc1, commits to 3.7 will go to 3.7.5+, the future 3.7.6, and will not disturb 3.7.5rc1 until Ned cherry picks them into the rc branch for 3.7.5.
Similarly, 3.8 is currently 3.8.b4+. As soon as you make 3.8.0rc1, if you do it the same way x.y.0rc1 has been done before recently, 3.8 commits should go to 3.8.0+, the future 3.8.1. Nothing should go into 3.8.0 until you pull it in or authorize it for those who know how to put it there (I don't). There should be no need to halt 3.8 activity.
tjr _______________________________________________ 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/IDOZFUKWL2JRFVNZVGXLWBHDSYKQEBII/ Code of Conduct: https://www.python.org/psf/codeofconduct/
