Open Stack

Rossella Sblendido <rsblendido at suse.com> wrote:

>
>
> On 03/23/2016 05:52 PM, Ihar Hrachyshka wrote:
>> Hey folks,
>>
>> some update on proactive backporting for neutron, and a call for action
>> from subteam leaders.
>>
>> As you probably know, lately we started to backport a lot of bug fixes
>> in latest stable branch (liberty atm) + became more systematic in
>> getting High+ bug fixes into older stable branch (kilo atm).
>>
>> I work on some tooling lately to get the process a bit more straight:
>>
>> https://review.openstack.org/#/q/project:openstack-infra/release-tools+owner:%22Ihar+Hrachyshka+%253Cihrachys%2540redhat.com%253E%22
>>
>>
>> I am at the point where I can issue a single command and get the list of
>> bugs fixed in master since previous check, with Wishlist bugs filtered
>> out [since those are not applicable for backporting]. The pipeline looks
>> like:
>>
>> ./bugs-fixed-since.py neutron <prevhash> |
>> ./lp-filter-bugs-by-importance.py --importance=Wishlist neutron |
>> ./get-lp-links.py
>>
>> For Kilo, we probably also need to add another filter for Low impact bugs:
>>
>> ./lp-filter-bugs-by-importance.py --importance=Low neutron
>>
>> There are more ideas on how to automate the process (specifically, kilo
>> backports should probably be postponed till Liberty patches land and be
>> handled in a separate workflow pipeline since old-stable criteria are
>> different; also, the pipeline should fully automate ‘easy' backport
>> proposals, doing cherry-pick and PS upload for the caller).
>
> Wow, great work, thanks a lot!
>
>> However we generate the list of backport candidates, in the end the bug
>> list is briefly triaged and categorized and put into the etherpad:
>>
>> https://etherpad.openstack.org/p/stable-bug-candidates-from-master
>>
>> I backport some fixes that are easy to cherry-pick myself. (easy == with
>> a press of a button in gerrit UI)
>>
>> Still, we have a lot of backport candidates that require special
>> attention in the etherpad.
>>
>> I ask folks that cover specific topics in our community (f.e. Assaf for
>> testing; Carl and Oleg for DVR/L3; John for IPAM; etc.) to look at the
>> current list, book some patches for your subteams to backport, and make
>> sure the fixes land in stable.
>
> I've gone through the L2 and ML2 section. I backported missing patches
> and added comments where I think no backport is needed.

Thanks Rossella!

I hope that others will join the effort too. If everyone takes one or two  
patches from the list, it should be low effort for everyone and great  
impact for our users.

Thanks again,
Ihar