MarkFinkle (talk | contribs) |
(→QA) |
||
(8 intermediate revisions by 5 users not shown) | |||
Line 12: | Line 12: | ||
== Major Topics for This Week == | == Major Topics for This Week == | ||
* Wrapping Beta 3 | |||
** Remaining [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking-fennec%3A2.0b3+ b3 blockers] | |||
** Sync/JPAKE | |||
** Content Crash Reporting | |||
** L10N / Packaging | |||
** IME regressions | |||
== Front-end == | == Front-end == | ||
* Beta 3 stuff | |||
** Sync/JPAKE | |||
** Content Crash UI | |||
** IME Regressions | |||
* Moving ahead to [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking-fennec%3A2.0b4+ b4 blockers] and [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking-fennec%3A%222.0%2B%22 final blockers] | |||
** Final blocker list will be triaged next week. Anything pushed will be moved to the next release (post 4.0) | |||
=== UX design === | === UX design === | ||
Line 22: | Line 34: | ||
== Android == | == Android == | ||
* Keyboard fixes landed ({{bug|599811}}, {{bug|581596}}); some regressions being worked on. | |||
* still waiting for packaging and multilocale repack stuff | |||
== Electrolysis == | == Electrolysis == | ||
Line 48: | Line 62: | ||
== QA == | == QA == | ||
* New Bugs over the week: [http://bit.ly/gloFWw filed]. Still at [http://bit.ly/9IXAxA 16 blockers] | |||
* Cross-browser Performance tests are done. Check out the [https://spreadsheets.google.com/ccc?key=0AocUyLHteCtSdDJrNkZFaE1kUktlUGItRktJXzB5ZVE&hl=en&authkey=CLz_9McK#gid=1 results] | |||
* Working on defining a [https://spreadsheets.google.com/ccc?key=0AocUyLHteCtSdFBIS2VWcDNocjhiNVNpYkM0SHh2YVE&hl=en&authkey=CN-b8NEH Device Compatibility testplan] for beta 3+. Work in progress. | |||
* Results from [https://wiki.mozilla.org/QA/Fennec/Waverley#Results nightly Smoketest runs] | |||
* Input: Manufacturer and Device are being sent to staging database and registering those fields correctly. Next step is to make it available on the dashboard. | |||
== Automation == | |||
* first regression was found and fixed on maemo mochitests! | |||
* I have a local fix for xpcshell on n900, will roll out next week in staging when releng starts coming back online | |||
* talos patches have landed for android fixes, installs are working but some devices are failing (investigating ways to reduce hung boards) | |||
== Other == | == Other == |
Latest revision as of 17:41, 24 November 2010
Details
- Wednesdays - 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
- 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 8605 (US)
- irc.mozilla.org #mobile for backchannel
Schedule
- Beta 3
- Code freeze: Nov 23 (slushy)
- Beta 4 (need dates)
Major Topics for This Week
- Wrapping Beta 3
- Remaining b3 blockers
- Sync/JPAKE
- Content Crash Reporting
- L10N / Packaging
- IME regressions
Front-end
- Beta 3 stuff
- Sync/JPAKE
- Content Crash UI
- IME Regressions
- Moving ahead to b4 blockers and final blockers
- Final blocker list will be triaged next week. Anything pushed will be moved to the next release (post 4.0)
UX design
Maemo
Qt
Android
- Keyboard fixes landed (bug 599811, bug 581596); some regressions being worked on.
- still waiting for packaging and multilocale repack stuff
Electrolysis
General Platform
Video
Camera
Plugins
Performance
Networking
Graphics
Startup
Layout
Content
Release Engineering
QA
- New Bugs over the week: filed. Still at 16 blockers
- Cross-browser Performance tests are done. Check out the results
- Working on defining a Device Compatibility testplan for beta 3+. Work in progress.
- Results from nightly Smoketest runs
- Input: Manufacturer and Device are being sent to staging database and registering those fields correctly. Next step is to make it available on the dashboard.
Automation
- first regression was found and fixed on maemo mochitests!
- I have a local fix for xpcshell on n900, will roll out next week in staging when releng starts coming back online
- talos patches have landed for android fixes, installs are working but some devices are failing (investigating ways to reduce hung boards)