Mobile/Notes/28-Jul-2010: Difference between revisions

From MozillaWiki
< Mobile‎ | Notes
Jump to navigation Jump to search
No edit summary
 
(21 intermediate revisions by 10 users not shown)
Line 11: Line 11:


== Front-end ==
== Front-end ==
* Bug fix mode
** Fixing reported bugs
** Fixing blockers for alpha 1
** Fixing broken browser-chrome tests
** Several e10s related patches are very close to landing, including some e10s crashers
* Feature mode
** [[Mobile/Planning/2.0 | Planning]] work has begun and some work has already landed
** mbrubeck starting work on sharing; bugs added to [[Mobile/Projects/Sharing]]
* Cleanup mode
** Updating front-end code to current trunk style
** Re-organizing some areas
* Updated more status and details for [[Mobile/Planning/2.0 | Planning 2.0]] tasks


=== UX design ===
=== UX design ===
Line 24: Line 36:
* {{bug|550936}} (InstallTrigger) ready to land once an xpconnect bug, {{bug|582100}} is done (which they say should be soon)
* {{bug|550936}} (InstallTrigger) ready to land once an xpconnect bug, {{bug|582100}} is done (which they say should be soon)
* {{bug|573635}} has two ways to resolve it, and we have patches for both. Neither is perfect but a perfect solution requires fundamental work on IPC networking. So for now, just need to decide which of the 2 patches to go with.
* {{bug|573635}} has two ways to resolve it, and we have patches for both. Neither is perfect but a perfect solution requires fundamental work on IPC networking. So for now, just need to decide which of the 2 patches to go with.
* place bugs getting closer to land.
* necko e10s reviews going faster. (12 patches in review state, 1 ready to push)
* removing real widgets soon in the child process
* window.crypto
* lots of warnings+errors in startup


== General Platform ==
== General Platform ==
Line 39: Line 56:


=== Performance ===
=== Performance ===
* Started [https://wiki.mozilla.org/Mobile/PowerManagement wiki page] on device and application states/notices by OS ('low battery', 'screen dimmed', 'application in background', etc.), need data from Android people please.


=== Networking ===
=== Networking ===
Line 47: Line 66:


=== Layout ===
=== Layout ===
* Where are we with [[Mobile/Layers | Layers]]
** Retained layers code has created some bugs in Fennec {{bug|579349}}
** "Fake widgets" finished wrt drawing, need event/focus/IME love {{bug|582057}}
** "Remote frames" for cross-process layers working with test-ipc, will be up for review today
* Bugs to watch
** Tracking bug {{bug|574512}}
** e10s shadow tree {{bug|570620}}
** <s>Integrate chrome hierarchy {{bug|130078}}</s> (fake widgets make this bug mostly irrelevant to fennectrolysis+browser)


=== Content ===
=== Content ===


== Release Engineering ==
== Release Engineering ==
* {{bug|562843}} Android release signing: looks like we can't renew certs. http://code.google.com/p/android/issues/detail?id=10020
* {{bug|567827}} make buildsymbols breaks on ix boxes: should land this week or early next
* most of n810s/n900s back in production
** {{bug|579184}} fixed: now unit tests with 0 passed tests are orange
** {{bug|579186}} Mozilla-central N810 builds do not launch (GLIBCXX_3.4.9 not found)
** {{bug|578343}} talos needs to be retrofitted for e10s
** {{bug|575506}} trunk maemo fennec builds not exiting talos profile creation since 6/23
** {{bug|582336}} (IT) Frequent "no route to host" in RF room -- main cause of reds.


== QA ==
== QA ==
=== Manual ===
* bugs [http://bit.ly/9o15HO filed] on the Fennec product over the past week
* Fx Input is mobile ready and will be pushed live tomorrow.
* working on triaging broken/unclear/failed test reports on litmus
* ahoza will be working on Find in page functionality testing
* Dates/Times related to Alpha 1?
* bug notes
** {{bug|579349}} - is still a blocker for testing
** {{bug|581532}} - Pages now load again with browser.tabs.remote=true, so testing again with that enabled. I'm getting crashes when closing tabs, in that case, though.
** (mw22) Found {{bug|582242}} crasher. It seemed to be Windows only, though.
=== Automation ===
** Android
*** Landed everything for mochitest/reftest on m-c
*** Patches in place for mochitest chrome/browser-chrome on android (need to be in a .jar file {{bug|543800}})
*** Working with bear this week to get heartbeat and device management into tinderbox
*** Fixing little bugs along the way
** Browser-Chrome {{bug|553474}}
*** handful of fixes to get tests working in e10s (thanks mfinkle, vingtetun)
*** lots of progress on new tests
*** still have an issue with 'too much recursion' causing all the tests to timeout
** [[https://wiki.mozilla.org/Mobile/Fennec_Unittests/green Green]]
*** mw22 and jmaher started looking into mochitest failures...the ball is rolling


== Other ==
== Other ==

Latest revision as of 16:59, 28 July 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

Major Topics for This Week

Front-end

  • Bug fix mode
    • Fixing reported bugs
    • Fixing blockers for alpha 1
    • Fixing broken browser-chrome tests
    • Several e10s related patches are very close to landing, including some e10s crashers
  • Feature mode
  • Cleanup mode
    • Updating front-end code to current trunk style
    • Re-organizing some areas
  • Updated more status and details for Planning 2.0 tasks

UX design

Maemo

Qt

Android

Electrolysis

  • bug 550936 (InstallTrigger) ready to land once an xpconnect bug, bug 582100 is done (which they say should be soon)
  • bug 573635 has two ways to resolve it, and we have patches for both. Neither is perfect but a perfect solution requires fundamental work on IPC networking. So for now, just need to decide which of the 2 patches to go with.
  • place bugs getting closer to land.
  • necko e10s reviews going faster. (12 patches in review state, 1 ready to push)
  • removing real widgets soon in the child process
  • window.crypto
  • lots of warnings+errors in startup

General Platform

Geolocation Working Group

Video

Camera

  • Layout bindings landed Bug 567323
  • Raw decoder relanded, looks like it will stick this time. Bug 508082
  • Have 95% of a patch to eliminate the temporary file and teach the DOM how to properly deal with a file generated by the camera. Chasing test failures down.

Plugins

Performance

  • Started wiki page on device and application states/notices by OS ('low battery', 'screen dimmed', 'application in background', etc.), need data from Android people please.

Networking

Graphics

Startup

Layout

  • Where are we with Layers
    • Retained layers code has created some bugs in Fennec bug 579349
    • "Fake widgets" finished wrt drawing, need event/focus/IME love bug 582057
    • "Remote frames" for cross-process layers working with test-ipc, will be up for review today
  • Bugs to watch
    • Tracking bug bug 574512
    • e10s shadow tree bug 570620
    • Integrate chrome hierarchy bug 130078 (fake widgets make this bug mostly irrelevant to fennectrolysis+browser)

Content

Release Engineering

QA

Manual

  • bugs filed on the Fennec product over the past week
  • Fx Input is mobile ready and will be pushed live tomorrow.
  • working on triaging broken/unclear/failed test reports on litmus
  • ahoza will be working on Find in page functionality testing
  • Dates/Times related to Alpha 1?
  • bug notes
    • bug 579349 - is still a blocker for testing
    • bug 581532 - Pages now load again with browser.tabs.remote=true, so testing again with that enabled. I'm getting crashes when closing tabs, in that case, though.
    • (mw22) Found bug 582242 crasher. It seemed to be Windows only, though.

Automation

    • Android
      • Landed everything for mochitest/reftest on m-c
      • Patches in place for mochitest chrome/browser-chrome on android (need to be in a .jar file bug 543800)
      • Working with bear this week to get heartbeat and device management into tinderbox
      • Fixing little bugs along the way
    • Browser-Chrome bug 553474
      • handful of fixes to get tests working in e10s (thanks mfinkle, vingtetun)
      • lots of progress on new tests
      • still have an issue with 'too much recursion' causing all the tests to timeout
    • [Green]
      • mw22 and jmaher started looking into mochitest failures...the ball is rolling

Other

Retrieved from "https://wiki.allizom.org/index.php?title=Mobile/Notes/28-Jul-2010&oldid=241721"