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