Confirmed users
2,280
edits
QA/Browser Technologies/Meetings/2013-01-29: Difference between revisions
QA/Browser Technologies/Meetings/2013-01-29 (view source)
Revision as of 17:04, 29 January 2013
, 29 January 2013→Take aways for this week
Otilia.anica (talk | contribs) |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
** PTO Reminder: | ** PTO Reminder: | ||
*** Ioana Chiorean - PTO - 2 days on February 1st and 15th | *** Ioana Chiorean - PTO - 2 days on February 1st and 15th | ||
*** Andreea Pod - PTO - Feb 5th-6th | *** Andreea Pod - PTO - Feb 5th-6th | ||
*** Adrian Tamas - PTO - Feb 4th | *** Adrian Tamas - PTO - Feb 4th | ||
*** Catalin Suciu - PTO - Feb 6th-8th | *** Catalin Suciu - PTO - Feb 6th-8th | ||
| Line 63: | Line 63: | ||
<i> (eg. Status, top issues) </i> | <i> (eg. Status, top issues) </i> | ||
* SoftVision (Catalin) | * SoftVision (Catalin) | ||
*** | ***Created new testcases | ||
***Bug Verification | ***Bug Verification | ||
* Mozilla (Tony) | * Mozilla (Tony) | ||
= Goals Draft = | |||
== Q1 2013 Goals Draft == | |||
* Deliverables | * Deliverables | ||
** Goal: Qualify the deployment of Fennec Native for Android to Google Play | ** Goal: Qualify the deployment of Fennec Native for Android to Google Play | ||
*** {{new|}} Customization goal for partners (themes, bookmarks, about:home) | |||
*** {{new|}} Qualify Firefox Native 19, 20 for Android | *** {{new|}} Qualify Firefox Native 19, 20 for Android | ||
**** {{new|}} support deployment of Armv6 Device 600Mhz | **** {{new|}} support deployment of Armv6 Device 600Mhz | ||
***** evaluating lower device chip and memory requirements, and screen size. conducting a testplan that will qualify the lower requirement support | ***** evaluating lower device chip and memory requirements, and screen size. conducting a testplan that will qualify the lower requirement support | ||
**** {{new|}} support deployment of x86 devices (pending Google Play compatibility) | **** <strike>{{new|}} support deployment of x86 devices (pending Google Play compatibility)</strike> | ||
*** {{new|}} supporting WebRTC for Android Fennec (understand their roadmap and what needs testing | *** {{new|}} supporting WebRTC for Android Fennec (understand their roadmap and what needs testing | ||
*** {{new|}} supporting Marketplace for Android Fennec (Aaron confirm if this is a Q1 goal) | *** {{new|}} supporting Marketplace for Android Fennec (Aaron confirm if this is a Q1 goal) | ||
| Line 86: | Line 88: | ||
*** {{carry|}} Develop Automated and reporting coverage for website compatibility detection (what happened to Spade?) | *** {{carry|}} Develop Automated and reporting coverage for website compatibility detection (what happened to Spade?) | ||
** Goal: Increase interaction within the Mobile Community | ** Goal: Increase interaction within the Mobile Community | ||
** {{new|}} Posting monthly updates and involvment projects to blogs, social media, and newsgroups | *** {{new|}} Posting monthly updates and involvment projects to blogs, social media, and newsgroups | ||
*** Weekly blogposts (or communication method) on QMO on something exciting this week, crashers we're finding, useful URLs. Something that can be tweeted or blogged. We dont want static content. Focus more on forward facing versus status'y stuff. | **** Weekly blogposts (or communication method) on QMO on something exciting this week, crashers we're finding, useful URLs. Something that can be tweeted or blogged. We dont want static content. Focus more on forward facing versus status'y stuff. | ||
**** Reworking the QA/Fennec hierarchal wiki pages. They should be clear and organized as a Test Strategy should be. (summary, channel pages, localization, testplans and results for each build, a template for future releases, howTo steps for community, tutorials on flags and such) | ***** Reworking the QA/Fennec hierarchal wiki pages. They should be clear and organized as a Test Strategy should be. (summary, channel pages, localization, testplans and results for each build, a template for future releases, howTo steps for community, tutorials on flags and such) | ||
** {{new|}} provide documentation and how to write testcases for robocop | *** {{new|}} provide documentation and how to write testcases for robocop | ||
** {{new|}} Add a One-and-Done project per month | *** {{new|}} Add a One-and-Done project per month | ||
** {{new|}}} Identify and outreach to more new community members | *** {{new|}}} Identify and outreach to more new community members | ||
**** Cleanup the spam around armv6-testdrivers@ and mobile-testdrivers@ lists | |||
==Community == | ==Community == | ||
| Line 97: | Line 100: | ||
== Take aways for this week== | == Take aways for this week== | ||
* [SV] To discuss goals internally and come back with ideas on supporting goals. These will be discussed in this meeting next week. | |||
* [Adrian, SV]To send an email to Joel about automation environment (tegra boards) | |||
* [Catalin] Send an email to jrjm asking how to help on new BID train. | |||
* [Tony, Aaron, Kevin] Send updates regarding the goals to SV (if there are changes) | |||