[tc][all] Dropping py35 testing

Ghanshyam Mann gmann at ghanshyammann.com
Sun Apr 14 18:48:25 UTC 2019

Hello Everyone,

All the integration testing has been moved to Bionic[1] now and as discussed in the TC meeting[2],
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). 

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.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2] http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-07-21.00.html


More information about the openstack-discuss mailing list