Hi, The change is already approved by FESCo [0] although as mentioned at the change page, it is accepted for release candidate, so I guess I should open another ticket for FESCo if they agree for a beta version to be built in rawhide.
Copr builds are here [1] as well (although not announced in any mailing list yet). [0] https://fedoraproject.org/wiki/Releases/26/ChangeSet?rd=Releases/26 [1] https://copr.fedorainfracloud.org/coprs/cstratak/python-3.6/build/464733/ Regards, Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat ----- Original Message ----- From: "Nick Coghlan" <ncogh...@gmail.com> To: "Fedora Python SIG" <python-devel@lists.fedoraproject.org> Sent: Monday, October 17, 2016 8:19:28 AM Subject: Re: Python 3.6 beta release in F26 Rawhide? On 12 October 2016 at 21:15, Charalampos Stratakis <cstra...@redhat.com> wrote: > Hello Nick, > > Please feel free to edit the change proposal. I also fully agree to the > proposal you made at the link you provided. Currently I have in copr the > first beta, and also I can build the second beta as well if I exclude the > ensurepip test. > > I was actually thinking of adding python 3.6 in rawhide when rc1 was > released, but if that is too late, which pre-release would be ideal to be > built in rawhide? The earliest one we can get FESCo to approve as a system-wide change for Fedora 26 :) That probably means beta 3 at this point - that's due out in two weeks time (October 31), so we'd be seeking FESCo approval for the change and pre-release Rawhide testing plan either this Friday or next Friday. If we decide that timeline is too ambitious (accounting for the fact I'm on vacation next week), then we'd target beta 4 on November 21st, allowing: - COPR-based testing of b2 and b3 to minimise stability impact to F26 Rawhide - incorporation of F26 Rawhide feedback into the upstream 3.6.0rc1 FESCo may come back and say "No, stick with the original rc1 plan", in which case the approach would change to assume we'll carry a patch for the os.urandom warning until at least 3.6.1, but hopefully we can make the case that b4 will be stable *enough*, and that if there are unexpectedly compatibility bugs, we're much better off finding them while there's time to submit fixes for them back upstream. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
