Mobile/Notes/15-Sep-2010: Difference between revisions

→‎Major Topics for This Week: 20 second crash is Android only?
(→‎Major Topics for This Week: 20 second crash is Android only?)
 
(24 intermediate revisions by 9 users not shown)
Line 13: Line 13:


== Major Topics for This Week ==
== Major Topics for This Week ==
* Crashes
** {{bug|595868}} 20 second crash (garbage collection related?  Android only? We have stack traces on Android.)
** {{bug|596382}} N900 content crash (shows content for a little while)
** {{bug|596433}} Illegal instruction on Android (has a fix, needs a little work)
** {{bug|594563}}, {{bug|596482}} Regular expression on Android


== Front-end ==
== Front-end ==
Line 33: Line 39:


=== UX design ===
=== UX design ===
* Android theme work is ready for final review;  see it here:
http://www.flickr.com/photos/madhava_work/sets/72157624962763028/
** accompanying notes on their way
* finishing flow explanations for
** meego vkb
** android and meego sharing (just to be perfectly clear!)
** copy paste
The following set of bugs describes the changes to what's in the nightly front end to get to what we want.  In terms of screen layout, the android theme mockups (and bug) shows the changes required.


*Add-ons Manager
*Add-ons Manager
Line 38: Line 55:
**{{bug|594795}} - Add a "What's an Add-on" block to the Add-ons Manager
**{{bug|594795}} - Add a "What's an Add-on" block to the Add-ons Manager
*Sharing redesign
*Sharing redesign
** {{bug|596609}} - share items from the awesomescreen
**{{bug|596609}} - share items from the awesomescreen
** {{Bug|596615}} - autobookmark shared pages/links
**{{Bug|596615}} - autobookmark shared pages/links
**  
**{{Bug|596632}} - on n900, make sure that SMS and email are sharing options
*Awesomescreen
*Awesomescreen
** {{bug|596612}} - indicate "remote" pages in awesomescreen results
** {{bug|596612}} - indicate "remote" pages in awesomescreen results
** {{bug|596614}} - focusing the URL field on the awesomescreen should not visibly change categories
** {{bug|596614}} - focusing the URL field on the awesomescreen should not visibly change categories
**{{bug|596626}} - Use the vkb with "Go" button when on awesomescreen
**{{bug|596626}} - Use the vkb with "Go" button when on awesomescreen
**{{bug|594918}} - dismiss vkb as a user starts to pan the awesomelist
* Titlebar
* Titlebar
** {{bug|596617}} - stop button should be responsive
** {{bug|596617}} - stop button should be responsive
Line 67: Line 85:
** Compression may be difficult
** Compression may be difficult
* Investigating using gold {{bug|596024}}
* Investigating using gold {{bug|596024}}
* updater landed, aki testing on the server side
* we crash on startup


== Electrolysis ==
== Electrolysis ==
Line 75: Line 95:


== General Platform ==
== General Platform ==
* Valgrind on ARM making progress!  Go Julian!


=== Geolocation Working Group ===
=== Geolocation Working Group ===
Line 89: Line 111:


=== Networking ===
=== Networking ===
* Patches done for nsIEncodedChannel support in e10s (needed to get gzip/gunzip right for some cases), need review+landing, which should hopefully happen today.
* Working on Pause/Resume regression described in {{bug|596402}}
* Working w/ Honza on crash/assert-botch described in {{bug|596059}}


=== Graphics ===
=== Graphics ===
Line 99: Line 125:


== Release Engineering ==
== Release Engineering ==
* android update status -- in progress.
** patches look good but i'm uploading snippets to the wrong place -- i need to upload them to the *previous* nightly's buildid; same with release patches
** hoping to fix/review/land nightly patches today.
* android l10n -- will need to investigate how omnijar will change things
* android tests -- launching tests, running into remote logging issues
** bear to try using patches attached to bugs
*** android unit/talos tests testing with patch for {{bug|596132}} to finalize steps
** bug to order 10 tegras filed
* tinderbox greenness -- I suspect talos isn't crashing due to e10s?
** unit tests have been red/orange but hid them yesterday at Stuart's request


== QA ==
== QA ==
Line 104: Line 141:
* QA is having a work week, so take this opportunity to take to your 2.0 feature QA for anything that they should know.
* QA is having a work week, so take this opportunity to take to your 2.0 feature QA for anything that they should know.
* Notes:
* Notes:
** Builds are complete broken over the past 2-3 days. We can't provide any test coverage [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&chfieldto=Now&chfield=bug_status&query_format=advanced&chfieldfrom=2010-08-10&chfieldvalue=resolved&bug_status=RESOLVED&product=Fennec on a lot of bugs] until builds are actually stable. So why are we still landing front end things?
** Builds are complete broken over the past 2-3 days. We can't provide any test coverage [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&chfieldto=Now&chfield=bug_status&query_format=advanced&chfieldfrom=2010-08-10&chfieldvalue=resolved&bug_status=RESOLVED&product=Fennec on a lot of bugs] until builds are actually stable.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=595868 Builds are crashing]
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=595868 Builds are crashing]
**** Others: {{bug|596482}}, {{bug|596289}}, {{bug|596433}}, {{bug|594563}}
**** Others: {{bug|596482}}, {{bug|596289}}, {{bug|596433}}, {{bug|594563}}
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=596382 Pages don't load] because the content process crashes
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=596382 Pages don't load] because the content process crashes
*** Finally, why the hell is [https://bugzilla.mozilla.org/show_bug.cgi?id=596610 tinderbox green across the board] when all of our builds are crashing on startup?
*** Finally, why is [https://bugzilla.mozilla.org/show_bug.cgi?id=596610 tinderbox green across the board] when all of our builds are crashing on startup?
*** Finallyx2, why did we not branch before jagermonkey landed?
*** Finallyx2, why did we not branch before jagermonkey landed?
*** Finallyx3, where was the testing on ARM for jagermonkey before it landed?
*** Finallyx3, where was the testing on ARM for jagermonkey before it landed?
* New Bugs over the week: [http://bit.ly/97ReXI filed]
* New Bugs over the week: [http://bit.ly/97ReXI filed]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=591368 Beta Tester Tools] landed
* Results from [https://wiki.mozilla.org/QA/Fennec/Waverley#Results nightly Smoketest runs].
* Results from [https://wiki.mozilla.org/QA/Fennec/Waverley#Results nightly Smoketest runs].
* [http://quality.mozilla.org/qmo-news/2010/09/14/firefox-moible-2-beta-testday-results/ MobiFx Testday] Results
* [http://quality.mozilla.org/qmo-news/2010/09/14/firefox-moible-2-beta-testday-results/ MobiFx Testday] Results


=== Automation ===
=== Automation ===
* talos
** {{bug|582997}} - working patch for android and n900, r+ need to land.  YAY tpan/tzoom party time!
* android
** lots of little fixes in the patch queue now, sounds like :bear has done a lot of work as we are finding some of these little bugs now:)
* browser-chrome - need some attention, carryover from last week
** new test files {{bug|489163}} and {{bug|570706}} are blocked on awesomebar problem
** {{bug|593463}} - awesomescreen.js problem
* [[https://wiki.mozilla.org/Mobile/Fennec_Unittests/green#mochitest mochitest: green]]
** {{bug|590121}} - FIXED
** {{bug|590248}} and {{bug|587646}} account for 60% of known mochitest failures on n900!, no progress on these two bugs?!  Still no traction on this - WEEK #4!!!


== Other ==
== Other ==
canmove, Confirmed users
1,584

edits