<div dir="ltr">Yep, Roman,<div>mos LP project was just created. So let's inform everyone to use it for components bugs, and not forgetting about tags.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jun 19, 2014 at 9:37 AM, Roman Podoliaka <span dir="ltr"><<a href="mailto:rpodolyaka@mirantis.com" target="_blank">rpodolyaka@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi guys,<br>
<br>
Dmitry, I have nothing against using 'also affects', but<br>
unfortunately, it seems that Launchpad advanced search doesn't allow<br>
to filter by affected projects :( (my use case is to be able to list<br>
only bugs affecting Nova in MOS, and as long as we deploy stable<br>
releases rather than trunk, upstream Nova bugs aren't always<br>
applicable or just have lower priority for us).<br>
<br>
Mike, cool, I didn't know <a href="https://launchpad.net/mos" target="_blank">https://launchpad.net/mos</a> existed! I'm all<br>
for using it rather than spamming you guys with purely MOS/OS bugs :)<br>
So we should probably ask QAs to start filing those against MOS now.<br>
But per project tags can still be useful due to Launchpad advanced<br>
search limitations.<br>
<br>
Thanks,<br>
Roman<br>
<br>
On Thu, Jun 19, 2014 at 5:29 AM, Mike Scherbakov<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>> wrote:<br>
> Actually I agree on tagging bugs as Roman suggests.<br>
> If no one against, we can create official tags for every project (nova,<br>
> neutron, etc.) - as long as it simplifies life and easy to use, I'm all for<br>
> it.<br>
><br>
><br>
> On Thu, Jun 19, 2014 at 6:26 AM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>><br>
> wrote:<br>
>><br>
>> +1 to this approach.<br>
>> Actually we've just created separate LP project for MOS:<br>
>> <a href="https://launchpad.net/mos" target="_blank">https://launchpad.net/mos</a>,<br>
>> and all bugs related to openstack / linux code (not Fuel), should be<br>
>> tracked there.<br>
>> I still think that we should also adding other OpenStack projects by<br>
>> clicking on "also affects" where possible.<br>
>><br>
>><br>
>> On Thu, Jun 19, 2014 at 1:30 AM, Dmitry Borodaenko<br>
>> <<a href="mailto:dborodaenko@mirantis.com">dborodaenko@mirantis.com</a>> wrote:<br>
>>><br>
>>> Roman,<br>
>>><br>
>>> What do you think about adding OS projects into the bug as "also<br>
>>> affects"? That allows to track upstream and downstream state of the bug<br>
>>> separately while maintaing visibility of both on the same page. The only<br>
>>> downside is spamming the bug with comments related to different projects,<br>
>>> but I think it's a reasonable trade off, you can't have too much information<br>
>>> about a bug :)<br>
>>><br>
>>> -DmitryB<br>
>>><br>
>>><br>
>>> On Wed, Jun 18, 2014 at 2:04 AM, Roman Podoliaka<br>
>>> <<a href="mailto:rpodolyaka@mirantis.com">rpodolyaka@mirantis.com</a>> wrote:<br>
>>>><br>
>>>> Hi Fuelers,<br>
>>>><br>
>>>> Not directly related to bug squashing day, but something to keep in<br>
>>>> mind.<br>
>>>><br>
>>>> AFAIU, both MOS and Fuel bugs are currently tracked under<br>
>>>> <a href="https://bugs.launchpad.net/fuel/" target="_blank">https://bugs.launchpad.net/fuel/</a> Launchpad project page. Most bugs<br>
>>>> filed there are probably deployment-specific, but still I bet there is<br>
>>>> a lot of bugs in OS projects you run into. If you could tag those<br>
>>>> using OS projects names (e.g. you already have the 'neutron' tag, but<br>
>>>> not 'nova' one) when triaging new bugs, that would greatly help us to<br>
>>>> find and fix them in both MOS and upstream projects.<br>
>>>><br>
>>>> Thanks,<br>
>>>> Roman<br>
>>>><br>
>>>> On Wed, Jun 18, 2014 at 8:04 AM, Mike Scherbakov<br>
>>>> <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>> wrote:<br>
>>>> > Fuelers,<br>
>>>> > please pay attention to stalled in progress bugs too - those which are<br>
>>>> > In<br>
>>>> > progress for more than a week. See [1].<br>
>>>> ><br>
>>>> ><br>
>>>> > [1]<br>
>>>> ><br>
>>>> > <a href="https://bugs.launchpad.net/fuel/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on" target="_blank">https://bugs.launchpad.net/fuel/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on</a><br>
>>>> ><br>
>>>> ><br>
>>>> > On Wed, Jun 18, 2014 at 8:43 AM, Mike Scherbakov<br>
>>>> > <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>><br>
>>>> > wrote:<br>
>>>> >><br>
>>>> >> Thanks for participation, folks.<br>
>>>> >> Current count:<br>
>>>> >> New - 12<br>
>>>> >> Incomplete - 30<br>
>>>> >> Confirmed / Triaged / in progress for 5.1 - 368<br>
>>>> >><br>
>>>> >> I've not logged how many bugs we had, but calculated that 26 bugs<br>
>>>> >> were<br>
>>>> >> filed over last 24 hours.<br>
>>>> >><br>
>>>> >> Overall, seems to be we did a good job in triaging, but results for<br>
>>>> >> fixing<br>
>>>> >> bugs are not that impressive. I'm inclined to think about another<br>
>>>> >> run, let's<br>
>>>> >> say, next Tuesday.<br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >> On Tue, Jun 17, 2014 at 7:12 AM, Mike Scherbakov<br>
>>>> >> <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>> wrote:<br>
>>>> >>><br>
>>>> >>> Current count:<br>
>>>> >>> New - 56<br>
>>>> >>> Incomplete - 48<br>
>>>> >>> Confirmed/Triaged/In progress for 5.1 - 331<br>
>>>> >>><br>
>>>> >>> Let's squash as many as we can!<br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> On Mon, Jun 16, 2014 at 6:16 AM, Mike Scherbakov<br>
>>>> >>> <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>> wrote:<br>
>>>> >>>><br>
>>>> >>>> Fuelers,<br>
>>>> >>>> as we discussed during last IRC meeting, I'm scheduling bug<br>
>>>> >>>> squashing<br>
>>>> >>>> day on Tuesday, June 17th.<br>
>>>> >>>><br>
>>>> >>>> I'd like to propose the following order of bugs processing:<br>
>>>> >>>><br>
>>>> >>>> Confirm / triage bugs in New status, assigning them to yourself to<br>
>>>> >>>> avoid<br>
>>>> >>>> the situation when a few people work on same bug<br>
>>>> >>>> Review bugs in Incomplete status, move them to Confirmed / Triaged<br>
>>>> >>>> or<br>
>>>> >>>> close as Invalid.<br>
>>>> >>>> Follow <a href="https://wiki.openstack.org/wiki/BugTriage" target="_blank">https://wiki.openstack.org/wiki/BugTriage</a> for the rest (this<br>
>>>> >>>> is<br>
>>>> >>>> MUST read for those who have not done it yet)<br>
>>>> >>>><br>
>>>> >>>> When we are more or less done with triaging, we can start proposing<br>
>>>> >>>> fixes for bugs. I suggest to extensively use #fuel-dev IRC for<br>
>>>> >>>> synchronization, and while someone fixes some bugs - the other one<br>
>>>> >>>> can<br>
>>>> >>>> participate in review of fixes. Don't hesitate to ask for code<br>
>>>> >>>> reviews.<br>
>>>> >>>><br>
>>>> >>>> Regards,<br>
>>>> >>>> --<br>
>>>> >>>> Mike Scherbakov<br>
>>>> >>>> #mihgen<br>
>>>> >>>><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> --<br>
>>>> >>> Mike Scherbakov<br>
>>>> >>> #mihgen<br>
>>>> >>><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >> --<br>
>>>> >> Mike Scherbakov<br>
>>>> >> #mihgen<br>
>>>> >><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > --<br>
>>>> > Mike Scherbakov<br>
>>>> > #mihgen<br>
>>>> ><br>
>>>> ><br>
>>>> > _______________________________________________<br>
>>>> > OpenStack-dev mailing list<br>
>>>> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>> ><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> OpenStack-dev mailing list<br>
>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Dmitry Borodaenko<br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Mike Scherbakov<br>
>> #mihgen<br>
>><br>
><br>
><br>
><br>
> --<br>
> Mike Scherbakov<br>
> #mihgen<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mike Scherbakov<br>#mihgen<br><br>
</div>