<div dir="ltr">Fuelers,<div>as we discussed during last <a href="http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-06-12-16.01.html">IRC meeting</a>, I'm scheduling bug squashing day on Tuesday, June 17th.</div>

<div><br></div><div>I'd like to propose the following order of bugs processing:</div><div><ol><li>Confirm / triage <a href="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">bugs in New status</a>, assigning them to yourself to avoid the situation when a few people work on same bug</li>

<li>Review bugs in <a href="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">Incomplete status</a>, move them to Confirmed / Triaged or close as Invalid.</li>

<li>Follow <a href="https://wiki.openstack.org/wiki/BugTriage">https://wiki.openstack.org/wiki/BugTriage</a> for the rest (this is MUST read for those who have not done it yet)</li></ol><div>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.</div>

<div><br></div><div>Regards,</div>-- <br>Mike Scherbakov<br>#mihgen<br><br>
</div></div>