Confirmed users
6,361
edits
(→Notes) |
|||
(18 intermediate revisions by 4 users not shown) | |||
Line 11: | Line 11: | ||
** Thanks to Aaron for including onto our wiki. Faceless people, please upload a profile picture! | ** Thanks to Aaron for including onto our wiki. Faceless people, please upload a profile picture! | ||
*Fennec stuff | |||
* Releases | ** Releases | ||
** Merge and ship is next week. Is it actually merging/shipping the same day? if so, how are we handing test coverage here | *** Merge and ship is next week. Is it actually merging/shipping the same day? if so, how are we handing test coverage here | ||
** [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0/Beta_6#Bug_Fixes 6] - we good to go? The two bugs i dont see verified yet. | *** [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0/Beta_6#Bug_Fixes 6] - we good to go? The two bugs i dont see verified yet. | ||
** [https://wiki.mozilla.org/QA/Fennec/Milestones/7.0#Features_Tracked 7] - this the final feature list? Have we gotten QA contacts for each feature? | *** [https://wiki.mozilla.org/QA/Fennec/Milestones/7.0#Features_Tracked 7] - this the final feature list? Have we gotten QA contacts for each feature? | ||
** [https://wiki.mozilla.org/QA/Fennec/Milestones/8.0 8] - same for this one, i like the breakdown of the bugs. Have we gotten QA contacts for each feature? | *** [https://wiki.mozilla.org/QA/Fennec/Milestones/8.0 8] - same for this one, i like the breakdown of the bugs. Have we gotten QA contacts for each feature? | ||
** Fennec Automation - Martijn | |||
*** update on road to 100k tests | |||
**** layout/style/tests problems have been identified. 2 of them have been fixed (one by me, scrollbar issue). 1 on them, jmaher will try and fix before turning layout/style/tests/ on. The last one will probably just be turned off for mobile until the relevant bug for that one has been fixed. | |||
**** Next directory: editor/libeditor/html (this is a retry!) | |||
*** update on crowdsource addon work (still needs a name!) | |||
**** http://people.mozilla.com/~mwargers/extensions/testharness@starkravingfinkle.org.xpi - latest version | |||
**** Need to talk to jgriffin on how to report the results to brasstacks | |||
* | * BrowserID - James | ||
** | ** Basic overview of BrowserID: http://identity.mozilla.com/post/7616727542/introducing-browserid-a-better-way-to-sign-in | ||
** Technical overview of BrowserID: http://lloyd.io/how-browserid-works | |||
** Beta (QA) deployment environment | |||
*** Server: https://diresworb.org/ | |||
*** Client: http://beta.myfavoritebeer.org/ | |||
** QA test/tools environment - TBD | |||
*** This will be built out on id2.mtv1.dev.svc.mozilla.com as BrowserID server | |||
*** QA can then build any BrowserID-supported client to test against id2. | |||
** Weekly train | |||
*** Thursday deployments to Beta in parallel with newest release to Prod | |||
*** Active QA testing and regression happens the following Monday - Wednesday | |||
** Upcoming changes/enhancements: (much) better client-side and server-side UI, security review, session support Add-On, integration with Pancake | |||
** Current BrowserID support matrix (a work in progress): | |||
*** https://spreadsheets.google.com/spreadsheet/ccc?key=0ArxosXOjCBacdHNrWFdBQmE3RU0xRFFwMUcxQWdRcXc&hl=en_US | |||
* Keeping up with Content | * Keeping up with Content on Pages | ||
** QMO needs a doc facelift | ** QMO needs a doc facelift | ||
*** Services landing page - James | *** Services landing page - James | ||
Line 27: | Line 47: | ||
*** Sync docs and video - Tracy | *** Sync docs and video - Tracy | ||
** BT wiki needs a Mobile Firefox landing page. Will modifty it a bit like the [https://wiki.mozilla.org/QA/Browser_Technologies/Services Services QA] page. - Tony | ** BT wiki needs a Mobile Firefox landing page. Will modifty it a bit like the [https://wiki.mozilla.org/QA/Browser_Technologies/Services Services QA] page. - Tony | ||
* Tablet purchasing | |||
** File an IT bug, everyone on this team should have one | |||
** which ones? lets discuss | |||
= Project Status = | = Project Status = | ||
*Fennec (kevin, aaron) | |||
** Automation (martijn) | |||
*Sync | |||
** Client (Tracy) | |||
*** Signed off Sync 1.8 addon on AMO. EOL'd any extension users that are on Firefox 4 and on. | |||
*** phase 2 is deprecating from AMO | |||
*** client train this week had no qa fixes. 2 small bugs landed. | |||
** Server (James) | |||
*** The next Sync Server train is on hold due to some HW issues with the new Stage environment (what used to be called the Sync Load Test Cluster). | |||
*** When it arrives, it will actually be a "train of trains": four major deployments covering the following bugs: Bug 676109, 670946, 676296, 676351 | |||
** Load Testing (Owen) | |||
*Test pilot (tracy) | |||
** no updates | |||
*BrowserID (james) | |||
** The first weekly train happened this week - QA reported 18 issues. | |||
** The next weekly train will show up tomorrow Friday, with QA testing starting Monday. | |||
** Deployment to the Beta (QA) environment as part of the weekly train seems to be quite successful. | |||
*Pancake (Naoki) | |||
** User testing still being conducted | |||
** Some of the new UI has been implemented | |||
** Search still needs work | |||
** QA starting to test again | |||
** Stable site : pancake.mozillalabs.com | |||
** Account creation : http://pancake.mozillalabs.com/account/create | |||
*** soon to move to Browser ID | |||
*Open Web Apps (tchung) | |||
** Roadmap discussion next week with OWA team | |||
** lots of moving parts, need to determine what BT will own | |||
** Feature list: https://wiki.mozilla.org/Apps/Features | |||
= Round Table = | = Round Table = | ||
= Notes = | = Notes = | ||
* bug 678159 is likely not a blocker. will build without it, but still need a little more investigation | |||
* (kevin) ping release-drivers good to build on mozilla-release branch. | |||
* (kevin) get beta pushed to market. inform rel-drivers | |||
* need release notes worthy data. add 'relnote' to the keyword | |||
* (tony) send out an email about what tablets/phones should we have. go through IT or through reiumbursement? send to qa-staff |