[tc][stable] Changing stable branch policy

Ben Nemec openstack at nemebean.com
Wed Nov 20 14:49:23 UTC 2019

On 11/20/19 8:21 AM, Matt Riedemann wrote:
> That might mean people merge things on stable branches for their 
> projects that don't follow the guidelines but so be it.

Another interesting point that was made in Shanghai was that the initial 
review is only the first level where bad backports can be caught. Even 
if something merges, it still has to be proposed for release, at which 
point the release liaison or PTL should be looking at it, and then once 
the release is proposed the release team is going to look at the changes 
included. So there is a safety net if a reviewer makes a mistake.

More information about the openstack-discuss mailing list