It's that time for another reminder: code cutoffs for the last scheduled 
releases of 2019 are coming up soon.  They are a little earlier than usual to 
try to avoid the end-of-December rush of various holidays.  Ɓukasz will have 
more details forthcoming about **3.8.1rc1**.  For the **3.7 branch**, the 
cutoff for **3.7.6rc1** is scheduled for this coming Monday (2019-12-09) by the 
end of day AOE.  I have also now scheduled the cutoff for the next cumulative 
security source release for the **3.6 branch**, **3.6.10rc1**, for Monday as 
well.  Please review open issues and ensure that any that you believe need to 
be addressed in any of these releases are either resolved or marked as a 
**release blocker**.  Any assistance you can provide in helping resolve issues 
will be greatly appreciated.  As usual, following the rc1 cutoff, changes 
merged to the 3.7 branch will be released in **3.7.7** three months from now 
unless you mark the issue as a release blocker prior to **3.7.6 final**, 
planned for release on **2019-12-16**, and explain why the change should be 
cherry-picked into the final release.  And as always, any proposed changes for 
the 3.6 branch need to meet the criteria for security branches and require 
release manager approval to merge.

Thanks for your continued efforts!

3.8 release PEP: https://www.python.org/dev/peps/pep-0569/
3.7 release PEP: https://www.python.org/dev/peps/pep-0537/
3.6 release PEP: https://www.python.org/dev/peps/pep-0494/
Security branch criteria: 
https://devguide.python.org/devcycle/#security-branches

--
  Ned Deily
  n...@python.org -- []
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/GYGZGI5VHSRX7U5JXS7MDRQ6LEQGFTLM/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to