To clarify about #6 below: We need *everyone* focused on release-blocking bugs until they're gone entirely. As long as there are open blockers, you can help. Even if a blocker is owned, there's often testing and input that is useful. So please don't even peek at a P4 or non-blocking bug until we've hit zero blockers.
If you hit zero blockers and can't help in any other blockers, start testing your device, or desktop builds, and go find *more* bugs. We need to ensure we find all of the serious issues before release. And for your edification: Fantastically, nearly all bugs fixed in the last 7 days fall into the right categories below! The number of P1 bugs fixed *far* outstrip the P2 and P3, and the number of non-blocking bugs fixed is almost non-existent. We're focusing on the right things, and that's what's going to allow us to ship. Keep it up :) On Mon, Dec 3, 2012 at 8:08 AM, Alex Keybl <[email protected]> wrote: > [x-post to dev-b2g and dev-gaia] > > I'd like to clarify the work order we're looking for with v1 B2G bugs. > > 1) b-b+ and P1 priority with Critical severity (QA testing or dogfood > blockers) > 2) By priority, bugs marked with b-b+, the C2 milestone, and assigned to you > 3) Bugs marked with b-b+, the C2 milestone, and assigned to your team or in > your area of expertise (steal the bug, provide early feedback, review, etc.) > 4) C3 bugs marked with b-b+ and assigned to you, by priority > 5) Any other b-b+ bugs > 6) blocking-basecamp- bugs with a P4 priority ("soft blockers") - last > priority, if there is somehow no b-b+ bugs to work on > > If you have any questions, please let us know. If you've got a bug in that > 5th category that needs to be handled sooner, let us know so that we can > milestone it into C2. Thanks! > > -Alex > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
