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_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 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=-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 < >> 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=-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 >> >> > > > -- > 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