It's worth noting here that the schedule is a tight fit with the Fedora 31 schedule as proposed. However, the feature freeze upstream is early enough that it should give us a long runway for testing. Still, it may be worth explicitly getting sign-off from QA.

Looking at the change list, 3.8 could easily be called a minor release. Apart from walrus, it's mostly a bunch of cleanups and depreciations. There are some incompatible changes, but they are minimal. Even with the tight schedule, I don't expect any issues with the upgrade.

+1

Note that there could still be more changes. We'd appreciate input form QA as well.

+1

QA impact ticket https://pagure.io/fedora-qa/issue/582

+1 here.

We're still waiting for an answer in #582 (expected today).

Would be interesting to know how close expected and actual schedules were for Python-3.7 and Python-3.6. We can't delay Fedora arbitrarily waiting for a 3.8 final release, so if the Python release slips more than a few weeks, we'd probably end up shipping a pre-release. I think that's basically OK as a low-probability thing, but we shouldn't plan on doing that.

AFAIK 3.7 slipped 12 days. https://github.com/python/peps/commit/15c4e471d0d29acd0389ebe7bec94116aea68b28

AFAIK 3.6 slipped 13 days.
https://github.com/python/peps/commit/deb80170575928880502a5fde4568a045409b032

+1

https://pagure.io/fedora-qa/issue/582

"QA is generally OK with this Change in principle, we are somewhat concerned at the timing and would be happiest if the Python 3.8 release winds up happening before the Fedora 31 Final freeze."

Consider me +1 as well.

+1

@bookwar, @sgallagh, @otaylor, @psabata?

+1

+1

I've deferred this to Fedora 32.

:broken_heart:

Probably the right decision, but still sad.