Upgrading Python from 3.N-1 to 3.N
Here are the notes from upgrading Python form 3.6 to 3.7. Those are created to save us time next time when upgrading to 3.8. It is not a comprehensive guide, but if it once get to it, it'd be great.
Create a Change Proposal
Before anything can happen, we need to create a Change Proposal. Follow the normal procedure, get inspired by previous changes, but make sure the process haven't changed (copypasta is good, but check if the template hasn't been updated).
Create python3N package
This can happen as soon as the first alpha is released. If you have enough resources, try to do it even before.
The python3X packages are designed to have flat/nonflat switches since 
python36
Make a copr repo, bootstrap "important stuff" in it
Bootstrapping Python packages is nontrivial. Chances are high that form the upgrade to 3.N-1, the bootstrap sequence has changed, as more packages switched to python3-sphinx etc. Start as early as possible.
For 3.7, I've used rpm-list-builder. The yaml recipe is archived on my GitHub. It has some comments. Note that rpm-list-builder has limitations:
- it doesn't bump releases, so you need to do that manually if you build one package once and the new build has new functionality (aka not just for tests)
- the "continue form here" future isn't very useful for us and was designed for different purpose, so what i did is that most of the yaml was commented out and I was uncommenting sections that i needed keeping finished stuff above, TODO stuff at the botttom
- everything is sequential. go do soemthing different form time to time
When
What wasn't done for 3.7 but might have been a good idea is to restart the procedure once in a while. Packages early in the bootstrap were build once with alphas and never tested with betas and rc. I suggest to restart the procedure on beta1 and on rc1.
Preserving the yaml recipe is good, you can use it for Fedora later.