On 10/30/19 4:20 PM, Barry Warsaw wrote:
On Oct 30, 2019, at 14:31, Łukasz Langa firstname.lastname@example.org wrote:
Yes. This allows for synchronizing the schedule of Python release management with Fedora. They've been historically very helpful in early finding regressions not only in core Python but also in third-party libraries, helping moving the community forward. It seems like a bargain to make a slight adjustment of our schedule to help Fedora help us make 3.9 and beyond better releases.
It would be really interesting for the major distros to work together, coordinating their archive rebuilds with the new/beta releases. E.g. Ubuntu might be ahead of Fedora, or vice versa, for any particular new Python release. Rebuilding the whole archive with the new version as default always uncovered interesting issues. It seems like we have a great untapped resource to find good signals as to bugs, breakages, regressions, and other problems during the Python beta process. How can that be leveraged better?
Just slightly off topic (sorry Brett), but I have past experience with the effort to try and sync the release cycle of something significant with that of major distros - and it's just too hard. (What are major "the major distros" anyway? the enterprise ones are on a completely different cycle, and some have gone to rolling releases where there's really nothing to sync to). By all means, if it hurts nothing to go for a sync now, to take advantage of some synergies, great, but don't try enshrine it in a PEP as a requirement going forward, there will only be lots of pain as things start to skew. And they will.