[openstack-dev] [Fuel] Bug squashing day on June, 17

Mike Scherbakov mscherbakov at mirantis.com
Tue Jun 17 03:12:49 UTC 2014


Current count:
New - 56
Incomplete - 48
Confirmed/Triaged/In progress for 5.1 - 331
<https://bugs.launchpad.net/fuel/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.milestone%3Alist=63962&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&search=Search>

Let's squash as many as we can!


On Mon, Jun 16, 2014 at 6:16 AM, Mike Scherbakov <mscherbakov at 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=-importance&field.status%3Alist=NEW&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&search=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=-importance&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&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&search=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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140617/83ebd0f1/attachment.html>


More information about the OpenStack-dev mailing list