QA/Execution/Meetings/2008-11-05: Difference between revisions
Jump to navigation
Jump to search
| (7 intermediate revisions by 2 users not shown) | |||
| Line 13: | Line 13: | ||
* Testday and community outreach process (marcia, tracy) | * Testday and community outreach process (marcia, tracy) | ||
** Revamping testdays to once a month? | ** Revamping testdays to once a month? | ||
** '''Discussion''' - create a test week for feature testing, and end with a testday | |||
** Track volunteers and issue rewards | |||
** Engage testers for a whole week of testing. Get people to try and do stuff on their own time. | |||
** Private Browsing, Ctrl Tab, Fennec Builds | |||
** Target the first week of December for PB '''(marcia)'''. meanwhile lets have a beta 2 testday next friday. | |||
* [https://wiki.mozilla.org/QA/Firefox3.1/TestPlan#QA_. | * [https://wiki.mozilla.org/QA/Firefox3.1/TestPlan#QA_.2F_Support_Team_Issues QA/Support Team issues] wiki page (tchung) | ||
** Use this section to enter top issues found in your nightly testing | ** Use this section to enter top issues found in your nightly testing | ||
** Reported updates to Cww | ** Reported updates to Cww | ||
** Should we create one similar for branch releases? | ** Should we create one similar for branch releases? '''Discussion''' - doesnt make much sense, since security testing is more about figuring out what needs to be fixed or not. | ||
*** Discover ways to get support with more release testing? We in turn could help with live chat? | |||
* QMO2 Update (jay, timr) | |||
** Rollback to old QMO | |||
** '''Discussion''' - late november would be back on track | |||
** Next steps, triage the issues found first. Finish this by friday | |||
** Jay will talk to contract agency and get them to fix P1 bugs | |||
** Fix all issues by 11/21, review the changes, and then repush | |||
= Project Updates = | = Project Updates = | ||
* Firefox 2.0.0.18/3.0.4 (abillings) | * Firefox 2.0.0.18/3.0.4 (abillings) | ||
** We are now in beta. Will target live on 11/12 | |||
** 2.0.0.19 / 3.0.5 - beta 12/9, ship 12/16 | |||
* Thunderbird 2.0.0.18 (abillings) | |||
** Builds next week, most bugs already verified | |||
** ship 12/19 | |||
* Firefox 3.1 (tchung) | * Firefox 3.1 (tchung) | ||
| Line 30: | Line 49: | ||
* Webdev update (stephend) | * Webdev update (stephend) | ||
** AMO 3.0.4 | ** [https://wiki.mozilla.org/Update:Remora_Meeting_Notepad#Nov_5 AMO 3.0.4] | ||
*** Code freeze on Nov. 10, shipping the 13th | *** Code freeze on Nov. 10, shipping the 13th | ||
** SUMO 0.7.2 | ** [https://wiki.mozilla.org/Support/SUMOdev_Meeting_Notepad#November_4_2008 SUMO 0.7.2] | ||
*** Code freeze on Nov. 7, shipping the 14th | *** Code freeze on Nov. 7, shipping the 14th | ||
** [https://wiki.mozilla.org/CommunityStore/QA/Test_Plan Community Store] | |||
*** In progress, waiting on template/form work before beginning testing | |||
* Mobile update (joelm) | * Mobile update (joelm) | ||
Latest revision as of 22:16, 5 November 2008
« previous mtg | index | next mtg »
Congratulations to President (Elect) Obama!
Discussion Items
- QA Q4 Work Week (tchung)
- Dec 8-12
- Wants and ideas
- Testday and community outreach process (marcia, tracy)
- Revamping testdays to once a month?
- Discussion - create a test week for feature testing, and end with a testday
- Track volunteers and issue rewards
- Engage testers for a whole week of testing. Get people to try and do stuff on their own time.
- Private Browsing, Ctrl Tab, Fennec Builds
- Target the first week of December for PB (marcia). meanwhile lets have a beta 2 testday next friday.
- QA/Support Team issues wiki page (tchung)
- Use this section to enter top issues found in your nightly testing
- Reported updates to Cww
- Should we create one similar for branch releases? Discussion - doesnt make much sense, since security testing is more about figuring out what needs to be fixed or not.
- Discover ways to get support with more release testing? We in turn could help with live chat?
- QMO2 Update (jay, timr)
- Rollback to old QMO
- Discussion - late november would be back on track
- Next steps, triage the issues found first. Finish this by friday
- Jay will talk to contract agency and get them to fix P1 bugs
- Fix all issues by 11/21, review the changes, and then repush
Project Updates
- Firefox 2.0.0.18/3.0.4 (abillings)
- We are now in beta. Will target live on 11/12
- 2.0.0.19 / 3.0.5 - beta 12/9, ship 12/16
- Thunderbird 2.0.0.18 (abillings)
- Builds next week, most bugs already verified
- ship 12/19
- Firefox 3.1 (tchung)
- QA Blocking Beta 2 issues. Please add if missing
- Testplan and assignments
- Tracking Status page
- Beta 2 slush freeze: 11/4
- Beta 2 hard freeze: 11/6
- Webdev update (stephend)
- AMO 3.0.4
- Code freeze on Nov. 10, shipping the 13th
- SUMO 0.7.2
- Code freeze on Nov. 7, shipping the 14th
- Community Store
- In progress, waiting on template/form work before beginning testing
- AMO 3.0.4
- Mobile update (joelm)
- Mobile dev is focused on performance and Windows Mobile
- Process started for adding mochitests to buildbot on Nokia device
- Investigating rest of automation that buildbot runs to include
- Initial test plan development for Alpha 2 release
- Acquiring devices for Windows Mobile testing
- Accessibility update (MarcoZ)
Other topics?