Shipping 3.X.5 or 3.X.6 would certainly make things much easier and help with exhaustion. However Fedora would no longer be driving early adaption of new Python 3.X versions in various upstream projects as it currently does and I’ve always consider that as a benefit for the larger Python ecosystem, not to Fedora itself. This actually sounds like a big drawback over the current situation.
Some datapoints:
- Fedora 29 Final was shipped with 3.7.0.
- Fedora 26 Final was shipped with 3.6.1.
- Fedora 24 Final was shipped with 3.5.1.
- Fedora 21 Final was shipped with 3.4.1.
- Fedora 18 Final was shipped with 3.3.0.
- Fedora 15 Final was shipped with 3.2(.0).
We wanted to ship 3.8.0 in Fedora 31 but didn’t make it, due to the closely misaligned schedules. I want to avoid this in the future, but the current annual release cycle proposal makes it permanent.
When we switch packages to new Python version, we often discover bugs. I’d rather help them discover during betas than during 3.X.5.
Having Fedora and Python release schedules closely aligned (as it happens e.g. with Fedora and GNOME) would IMHO be hugely beneficial to both projects. Having Python releases scheduled as proposed is the worst possible combination with Fedora’s schedule – it either creates an impossible race we cannot win, or it drops the benefits that were present with the “adapt soon” Fedora’s Python relationship so far.
What is the maximum amount of days this can be moved? Is it 0?
We can certainly live on the edge. I just don’t want to satisfy with permanent misalignment.