[tc][stable] Changing stable branch policy

Thierry Carrez thierry at openstack.org
Tue Nov 19 11:05:28 UTC 2019

Ghanshyam Mann wrote:
> [...]
> I am still finding difficult to understand the change and how it will solve the current problem.
> The current problem is:
> * Fewer contributors in the stable-maintenance team (core stable team and project side stable team)
>   which is nothing but we have fewer contributors who understand the stable policies.
> * The stable policies are not the problem so we will stick with current stable policies across all the projects. 
>   Stable policies have to be maintained at single place for consistency in backports across projects.
> [...]
I don't think that this the problem this change wants to solve.

Currently the stable-core team is perceived as a bottleneck to getting 
more people into project-specific stable teams, or keeping those teams 
membership up to date. As a result stable maintenance is still seen in 
some teams as an alien thing, rather than an integral team duty.

I suspect that by getting out of the badge-granting game, stable-core 
could focus more on stable policy definition and education, and review 
how well or bad each team does on the stable front. Because reviewing 
backports for stable branch suitability is just one part of doing stable 
branch right -- the other is to actively backport relevant patches.

Personally, the main reason I support this change is that we have too 
much "ask for permission" things in OpenStack today, something that was 
driven by a code-review-for-everything culture. So the more we can 
remove the need to ask for permission to do some work, the better.

Thierry Carrez (ttx)

More information about the openstack-discuss mailing list