<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 15, 2018 at 3:01 PM Zane Bitter <<a href="mailto:zbitter@redhat.com">zbitter@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/10/18 8:59 AM, Corey Bryant wrote:<br>
> <br>
> <br>
> On Thu, Oct 11, 2018 at 10:19 AM Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a> <br>
> <mailto:<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>>> wrote:<br>
> <br>
> On 10/10/2018 23.10, Jeremy Stanley wrote:<br>
> > I might have only pointed this out on IRC so far, but the<br>
> > expectation is that testing 3.5 and 3.6 at the same time was merely<br>
> > transitional since official OpenStack projects should be moving<br>
> > their testing from Ubuntu Xenial (which provides 3.5) to Ubuntu<br>
> > Bionic (which provides 3.6 and, now, 3.7 as well) during the Stein<br>
> > cycle and so will drop 3.5 testing on master in the process.<br>
> <br>
> Agreed, this needs some larger communication and explanation on what<br>
> to do,<br>
> <br>
> <br>
> The good news is we now have an initial change underway and successful, <br>
> dropping py35 and enabling py37: <a href="https://review.openstack.org/#/c/609557/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/609557/</a><br>
<br>
Hey Corey,<br>
Thanks for getting this underway, it's really important that we keep <br>
moving forward (we definitely got behind on the 3.6 transition and are <br>
paying for it now).<br>
<br>
That said, I don't think we should be dropping support/testing for 3.5. <br>
According to:<br>
<br>
<a href="https://governance.openstack.org/tc/reference/pti/python.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/reference/pti/python.html</a><br>
<br>
3.5 is the only Python3 version that we require all projects to run <br>
tests for.<br>
<br>
Out goal is to get everyone running 3.6 unit tests by the end of Stein:<br>
<br>
<br>
<a href="https://governance.openstack.org/tc/goals/stein/python3-first.html#python-3-6-unit-test-jobs" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/goals/stein/python3-first.html#python-3-6-unit-test-jobs</a><br>
<br>
but we explicitly said there that we were not dropping support for 3.5 <br>
as part of the goal, and should continue to do so until we can effect an <br>
orderly transition later. Personally, I would see that including waiting <br>
for all the 3.5-supporting projects to add 3.6 jobs (which has been <br>
blocked up until ~this point, as we are only just now close to getting <br>
all of the repos using local Zuul config).<br>
<br>
I do agree that anything that works on 3.5 and 3.7 will almost certainly <br>
work on 3.6, so if you wanted to submit a patch to that goal saying that <br>
projects could add a unit test job for *either* 3.6 or 3.7 (in addition <br>
to 3.5) then I would probably support that. We could then switch all the <br>
3.5 jobs to 3.6 later when we eventually drop 3.5 support. That would <br>
mean we'd only ever run 3 unit test jobs (and 2 once 2.7 is eventually <br>
dropped) - for the oldest and newest versions of Python 3 that a project <br>
supports.<br></blockquote><div><br></div><div>This seems like a reasonable approach to me. I'll get a review up and we can see what others think.</div><div><br></div><div>Thanks,<br></div><div>Corey</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
cheers,<br>
Zane.<br>
<br>
[This thread was also discussed on IRC starting here: <br>
<a href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-10-15.log.html#t2018-10-15T18:09:05" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-10-15.log.html#t2018-10-15T18:09:05</a>]<br>
<br>
> I'm happy to get things moving along and start proposing changes like <br>
> this to other projects and communicating with PTLs along the way. Do you <br>
> think we need more discussion/communication on this or should I get started?<br>
> <br>
> Thanks,<br>
> Corey<br>
> <br>
> <br>
> Andreas<br>
> -- <br>
> Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a> <<a href="http://suse.com" rel="noreferrer" target="_blank">http://suse.com</a>>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a><br>
> <<a href="http://opensuse.org" rel="noreferrer" target="_blank">http://opensuse.org</a>>} Twitter: jaegerandi<br>
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
> HRB 21284 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272<br>
> A126<br>
> <br>
> <br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
> <br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>