B2G/Triage: Difference between revisions

B2G/Triage (view source)

Revision as of 11:06, 5 August 2015

1,225 bytes removed , 5 August 2015

→‎Special Issues that Should Block Spark v1

Joshwalker

Confirmed users

811

edits

@@ Line 264: / Line 264: @@
 * Do not file multiple issues in a single bug
 * Please make sure that whoever nominates a bug for blocking is available to promptly answer questions. Even better, please make sure to use one Bugzilla account per individual nominating.
-===Special Issues that Should Block Spark v1===
-Spark v1 (blocking-b2g: spark+/?) is triaged slightly differently from other releases as it's a dogfood-only release and the builds are shipped nightly from laterst master/central. Due to this we have an expanded criteria for spark releases that is outlined below :
-* Major issue in new feature - especially those in which a large number of users will be impacted, or a smaller number of users will be significantly impacted
-* Major identifiable regressions (perf or otherwise)
-* Top Crashes
-* sec-high, sec-critical security bugs
-* Smoke-test regression
-* Data loss
-* Issues getting a lot of support calls with desktop support, on SUMO, on Bugzilla (perhaps via BzLite), or on BuddyUp
-* Issues critical around updates (especially if there's been a repro)
-* Major Dialer, SMS, and VM communication issues
-* Issues that prevent automated tests in established testsuites (visible test suites on b2g integration branches on Treeherder) from running green at least 90% of the time.
-* Major issue with an embedded 3rd party app (in case it can't be solved, it could be decided to remove the app)
-* Any problems that dogfooders are likely to encounter and be seriously impacted by
 == Whiteboards & Flags ==

B2G/Triage: Difference between revisions

B2G/Triage (view source)

Revision as of 11:06, 5 August 2015

Navigation menu

Search