On 06/05/2018 02:55 PM, Zane Bitter wrote:
[snip]
The list of breaking changes in 3.6 is quite short (although not
zero), so I wouldn't expect too many roadblocks:
https://docs.python.org/3/whatsnew/3.6.html#porting-to-python-3-6
I think we can split the problem into two parts:
* How can we detect any issues ASAP.
Would it be sane to give all projects with a py35 unit tests job a
non-voting py36 job so that they can start fixing any issues right
away? Like this: https://review.openstack.org/572535
FWIW, Cinder has had py36 jobs running (and voting) for both unit tests
and functional tests for just over a month
now with no issues - https://review.openstack.org/#/c/564513/
* How can we ensure every project fixes any issues and migrates to
voting gates, including for functional test jobs?
Would it make sense to make this part of the 'python3-first'
project-wide goal?
+1
cheers,
Zane.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
