Open Stack

I forgot to "reply all"... Please see below.

On Mon, Sep 28, 2015 at 6:58 PM, Shamail Tahir <itzshamail at gmail.com> wrote:

>
>
> On Mon, Sep 28, 2015 at 6:03 PM, <Arkady_Kanevsky at dell.com> wrote:
>
>> Problem: Currently bug fixes take a long time especially for previous
>> releases.
>>
>> Proposal:
>>
>> 1.       For each project Product WG identify a couple of people ( at
>> least 3 overall to handle vacations and a like) among its member companies
>> who will have responsibility to review submitted bug fixes (for all
>> releases) within 1 day
>>
> I don't know if the majority of people in the Product WG have the
> necessary development/project background to conduct reviews.  It would be a
> better goal to set up a rotating schedule of member companies to provide
> developers to address bugs.  The list could rotate every month or so to
> reduce the overall burden on a single entity.
>
>>
>> 2.       These people will be added automatically as reviewers for each
>> bug patch submission.
>>
> Please see my comment on #1
>
>>
>> a.       Need some help with tool people to automatically add these
>> people as reviewers for newly filed bugs
>>
>> 3.       Once a patch has two +1 ones from these reviewers and no -1s
>> from anybody else, project PTL or project designated bug tsar will merge it
>> if it passes his/her review within 2 days
>>
> Establishing a time-frame will be hard because this will probably be
> relative to the overall number of reviews the core-team for that project
> has to conduct.  Ideally, we should leverage CPLs here to gather list of
> patch-sets that need review and bring them up at the project's weekly team
> meeting.
>
>>
>> a.       Need to agree on the mechanism to let PTL or designate know of
>> patch readiness. Maybe one of the reviewers adds PTL or designate to the
>> patch when passing baton criteria is met. (Best to run by PTLs and TC for
>> recommendation).
>>
> I would suggest using the Product WG CPLs for this.
>
>>
>> 4.       Have periodic bug scrub per project (weekly? Monthly?) and
>> choose small # of bugs to tackle for this period.
>>
> Monthly is probably a good starting point IMHO.
>
>>
>> 5.       Once we, Product WG, agree on the proposal, Rocky will present
>> it to PTL on cross functional meeting.
>>
> We probably should draft this in spec format and submit it to the
> cross-project specs repo before we get on the agenda.  We can then point to
> the review link during the actual conversation.
>
>>
>>
>> Comments please.
>>
>> Arkady Kanevsky, Ph.D.
>> Director of SW Development
>> Dell ESG
>> Dell Inc. One Dell Way, MS PS2-91
>> Round Rock, TX 78682, USA
>> Phone: 512 723 5264
>>
>> _______________________________________________
>> Product-wg mailing list
>> Product-wg at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>>
>
>
>
> --
> Thanks,
> Shamail Tahir
> t: @ShamailXD
> tz: Eastern Time
>



-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time