[tc][all] Dropping py35 testing
smooney at redhat.com
Mon Apr 15 13:59:51 UTC 2019
On Sun, 2019-04-14 at 13:48 -0500, Ghanshyam Mann wrote:
> Hello Everyone,
> All the integration testing has been moved to Bionic now and as discussed in the TC meeting,
> we are good to drop the py35 testing.
> Train: Good to drop.
> I am going to push the patches to remove the py35 jobs from the master (which is Train now).
so i asked this a number of months ago and at the time i did not get a concreate answer.
if we drop py35 testing that means we are increaseing our minium python 3 version to py36
so projects are free to use python 3.6 only feature correct once py2.7 support is removed.
i recently found out that nova does not work on py37 and if we have no testing for py35 then
its possible that we could also break there so if this goes ahead i want to carify that for train
the only supported python veriosn will by py27 and py36 unless we elect to add py37 support as a train
> Stable/Stein: Ok to drop if the project wants.
> Stable/Stein gate is also moved to Bionic so we are good to drop py35 from stable/stein too.
> But backporting all the patches will be too many patches for projects to merge on stable/stein so
> we discussed not to propose all of them to stable/stein. If the project really wants to drop it from
> stable/stein then, they can backport.
> NOTE: Till stable/rocky, we should keep testing py35. If your project is branchless like Tempest and gate
> the same jobs for stable/rocky or older then, you should keep testing the py35 until stable/rocky EOL.
>  http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
>  http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-07-21.00.html
More information about the openstack-discuss