Dropping python2.7 from diskimage-builder
Ian Wienand
iwienand at redhat.com
Thu May 21 04:22:48 UTC 2020
On Thu, May 21, 2020 at 08:22:42AM +1000, Ian Wienand wrote:
> Since dib is currently on version 2, perhaps we should tag as version
> 3 and then leave ourselves the option of a branch from that point, if
> we find we actually need it?
After a bit of discussion, I think [1] is ready; it keeps minimal
Python 3.5 support to keep inline with Zuul/nodepool by not using
constraints to test under 3.5, but then includes py36 onwards jobs as
usual.
Looking at bifrost, they seem to install from Zuul checkout, so just
adding a branch-override tag for the last 2.0 (2.37 I guess) to the
required-projects on stable branches should do it. johnsom confirmed
it would be OK for octavia.
Since [1] has a few dependencies anyway, I think it's probably best to
force-merge [2,3,4,5] around the gate failures (they'd had review from
clarkb and otherwise passing) which fixes some bits about installing
the focal kernel and will mean that the last 2.X does not have any
known issues building images up until the focal release.
-i
[1] https://review.opendev.org/728889
[2] https://review.opendev.org/727049
[3] https://review.opendev.org/727050
[4] https://review.opendev.org/726996
[5] https://review.opendev.org/725752
More information about the openstack-discuss
mailing list