osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[tc][all] Dropping py35 testing


 ---- On Mon, 15 Apr 2019 10:44:51 -0500 Ghanshyam Mann <gmann at ghanshyammann.com> wrote ----
 >  ---- On Mon, 15 Apr 2019 09:45:06 -0500 Zane Bitter <zbitter at redhat.com> wrote ---- 
 >  > On 14/04/19 2:48 PM, Ghanshyam Mann wrote:  
 >  > > 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).  
 >  >   
 >  > +1  
 >  >   
 >  > Can I suggest that you instead push patches to switch to   
 >  > openstack-python3-train-jobs?  
 >  >   
 >  > The only downside of that is that since it can't merge until py37 works,   
 >  > projects will end up continuing to run py35 tests until py37 support is   
 >  > ready to merge. But the upside is we only have to make one change for Train.  
 >  
 > I was thinking to update the Train runtime targets in 'openstack-python-jobs' project template 
 > which is already present on each project side. If we use this template to update testing 
 > runtime jobs each cycle then, we do not need to update all projects. 
 >  
 > Any drop of py version or addition will be done at a single place and with consistency.  

Another reason I kept it separate from Train testing runtime is that if any project wants to backport py35
dropping to stable/stein then, they can do with this patchset. 

-gmann

 >  
 > -gmann 
 >  
 >  >   
 >  > > 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  
 >  > >         http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003610.html  
 >  > >   
 >  > > -gmann  
 >  > >   
 >  > >   
 >  >   
 >  >   
 >  >  
 >