[b2g] 3/8/2013 Unagi Smoke Test Results - V1 Train - 39/46 tests passed, 2 Blockers (1 New), 2 Fails, 4 partial fails

*Hello Everyone, 39 out of 46 tests passed for the 3/08/2013 build. Here are the major issues that prevented the smoke tests from passing: * Smoketest: https://docs.google.com/

Re: [b2g] B2G QA's Triage Process for Addressing QA Requests

Updated the B2G QA triage wiki based on your feedback. I've now broken it into four categories and now have the highest urgency listed as "very high" that would have the SLA of three days optimally for initial response. Sincerely, Jason Smith Desktop QA Engineer Mozilla Corporation https://qua

[b2g] Performance uplifts

Hi all, The perf graphs (https://datazilla.mozilla.org/b2g/) for master generally look awesome, but much less so for 1.0.1 and v1-train. That means we've missed opportunities to uplift these big perf wins to where users will actually be able to take advantage of them. Our partners are eager fo

Re: [b2g] B2G QA's Triage Process for Addressing QA Requests

Hi Alex, Our team is aims to provide an initial response to requests on the high list within three days optimally. I'll add another priority also about the tracking? and tracking+ as well per your feedback. Sincerely, Jason Smith Desktop QA Engineer Mozilla Corporation https://quality.mozi

Re: [b2g] B2G QA's Triage Process for Addressing QA Requests

This is great - the queries you provided at https://wiki.mozilla.org/B2G/QA/Triage#Request_Urgency will definitely help joint triage and engineering understand priorities for testing. How regularly would you all expect to address requests from the High list? It's obviously case by case, but und

Re: [b2g] Update info: 3/6 V1 Train Build OK for dogfooders

Hal: To clarify, the 3/6 build can be promoted. Here is the updated info and apologies for the mistake. Updated from (Build to Promote): Build ID: 20130306070201 Gecko: bccf111e9131 Gaia: 77fb74ebf3bea340be9f8f4b4c9ac9dd7c12ab0b Updated to: Build ID: 20130307103636 Gecko: a0b06192f882 Gaia: f

[b2g] B2G QA's Triage Process for Addressing QA Requests

Hi Everyone, Our B2G QA team has put together a short wiki that summarizes how we will triage incoming requests for QA support here - https://wiki.mozilla.org/B2G/QA/Triage. This document aims to clarify what keywords to use in what situation, how the QA contact field is used, and our differe

Re: [b2g] Update info: 3/6 V1 Train Build OK for dogfooders

Marcia, Usually, we promote the "updated from" build, which is from 3/5. Your text cites 3/6. Could you please clarify which buildID is to be promoted to dogfooders? (Dogfooders are currently being offered the 3/4 build.) Thanks! --Hal On 2013-03-08 07:32 , Marcia Knous wrote: > 3/6 Build OK for

[b2g] Update info: 3/6 V1 Train Build OK for dogfooders

3/6 Build OK for dogfooders. Note that the update info email that was sent last night related to yesterday's build (3/7), which was a mistake (that one will not be promoted in any case due to a Gaia bug). Build updated from: - gecko:http://hg.mozilla.org/releases/mozilla-b2g18/rev/d9278721e

[b2g] 3/08/2013 Unagi Smoke Test Results - 33 pass, 8 fail, 2 untested

Hi Everyone, 33 out of 46 tests passed for the 3/08/2013 build. Here are the major issues that prevented the smoke tests from passing: * Smoketest: https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=75