[tc][all] Dropping py35 testing
---- On Mon, 15 Apr 2019 08:35:36 -0500 Moises Guimaraes de Medeiros <moguimar at redhat.com> wrote ----
> Hi Ghanshyam,
> I saw your patch on oslo.config and I notice that in the tox.ini file it drops Python 3 at all. Should we add py36 in the same patch before approving it?
> I'm sending this here cause it might also be the same case for other patches.
I did not explicitly added the py36 tox env in same patch which was not there. I thought it is intentional from the project side. But yeah we can modify the py35 env to py36
if there is no.
> Em dom, 14 de abr de 2019 Ã s 20:48, Ghanshyam Mann <gmann at ghanshyammann.com> escreveu:
> Thanks,MoisÃ©s GuimarÃ£es
> 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).
> 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