Perform 'blurb split' for 3.3. by larryhastings · Pull Request #2715 · python/cpython

I hear and obey--I'll hold off.

If any of the cherry-picks back into 3.3 have Misc/NEWS.d blurb entries, I guess you'll have two choices:

1. Manually merge them into Misc/NEWS, or
2. Run blurb split and blurb merge yourself as part of the release process, without checking in any of the intermediary files, just to regenerate Misc/NEWS. Then check your changes to Misc/NEWS in.
   This will have the happy side-effect of also updating your Misc/NEWS to the modern aesthetics (e.g. bpo-, section name "macOS").

I think 2. is the way to go, personally; it seems like a very sensible approach to handling the end-of-life 3.3 branch overall. Misc/NEWS will remain where it is so it won't affect the Doc build process.