An update: 3.7.0rc1 and 3.6.6rc1 are now tagged and we now move on to the final stages for 3.7.0 and for 3.6.6. The source code has been shipped to our factory (in a tariff-free zone!) where the elves will produce the final bits for the release. They promise to be done soon so stay tuned for the release announcements later today.
In the meantime, the 3.7 and 3.6 branches in the cpython repo are open for merges. As of the rc1 cutoffs (tags v3.7.0rc1 and v3.6.6rc1 in the cpython repo), expect merges to 3.7 to appear in 3.7.1 and merges to 3.6 to appear in 3.6.7. Please continue to treat the 3.7 branch as if it were already released and in maintenance mode. Please continue to pay attention to CI test failures and buildbot test failures and see if you can help resolve them. If you find something that may affect either final release, please make sure to open a new issue on bugs.python.org, or update an existing issue, and set the priority to "release blocker". As always, improving the documentation never ceases so keep those updates coming in. Prior to 3.7.0 final and 3.6.6 final, I will review doc changes that have been merged and consider cherry-picking them into the release materials. By the way, don't be fooled: if you build Python from the 3.7 branch at the moment, the version will be "3.7.0rc1+" but changes merged will be in 3.7.1; similarly for 3.6.
The clock is now ticking: 15 days until the final releases. Please do what you can to encourage exposure and testing by ourselves and our downstream users.
Once again, I want to thank everyone who has been involved so far in helping us through the 3.7 endgame and who have given up their personal time to work on making Python better. I remain deeply grateful.
-- Ned Deily email@example.com --