Platform/2012-05-08: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 15: Line 15:


==Kilimanjaro==
==Kilimanjaro==
* Kilimanjaro - Base Camp
** Communications at the MoCo meeting yesterday - pivoting Kilimanjaro around B2G goals.
** Product team working on defining "base camp".
** Posts to come on dev.planning.
** Proceeding with triage today at 11:30am PT.
* Web app/site compat
* Web app/site compat
** Will be pushing out a crowd sourcing mobile site test tool this week. Once announced please take the time to run through a few of the URLs and provide your feedback.
** Will be pushing out a crowd sourcing mobile site test tool this week. Once announced please take the time to run through a few of the URLs and provide your feedback.

Revision as of 16:36, 8 May 2012


« previous week | index | next week »

Platform Meeting Details

  • Tuesday 2012-05-08 - 11:00 am Pacific
  • Dial-in: Audio-only conference# 95312
    • People with Mozilla phones or softphones please dial x4000 Conf# 95312
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 95312
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 95312
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 95312
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 95312
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 95312
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 95312
    • UK/London: +44 (0)207 855 3000, x4000 Conf# 95312
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 95312
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • Warp Core Vidyo Room / SFO-Boardroom
  • join irc.mozilla.org #planning for back channel

Kilimanjaro

  • Kilimanjaro - Base Camp
    • Communications at the MoCo meeting yesterday - pivoting Kilimanjaro around B2G goals.
    • Product team working on defining "base camp".
    • Posts to come on dev.planning.
    • Proceeding with triage today at 11:30am PT.
  • Web app/site compat
    • Will be pushing out a crowd sourcing mobile site test tool this week. Once announced please take the time to run through a few of the URLs and provide your feedback.

Notices / Schedule

Firefox Development

Firefox Developer Tools

Add-on SDK

Performance

  • Perf work week May 14-18 (next week) in MV.
  • This week's Snappy summary
  • Bas is working on slow downs due to borders and gradients. We should see some improvement in 3-4 weeks.
  • Incremental GC should turned back on soon (bug 750424, bug 750416).
  • Kyle’s big memory leak fix from last week turned out to occasionally cause leaks where there were none before (bug 751466).
  • Tim moved thumbnail storage away from network cache, which reduces cache contention and browser freezes (bug 744388).
  • Paulo continued nuking sync favicon api usage (bug 728168).

GFX

JS

Layout

  • SVG and CSS working group meetings this week (including joint meeting Wednesday)
  • likely some large changes to font size inflation coming soon to increase the size of the areas in which we make separate inflation decisions (bug 707195 and duplicates/dependencies)

Video

DOM

WebAPI

Network

Identity

Plugins

Mobile

Accessibility

Tree Management

Security

Stability Report

Socorro

Desktop

Mobile

CrashStats 2012-05-07.png

  • Aurora top crashes are mostly libdvm crashes, bug 730890 was fixed in nightly, waiting aurora approval; remaining Libdvm bugs are as seen:
    • bug 751967 - crash on new tab/google maps galaxy nexus, ICS, 5.03 build
    • bug 751262 - Dalvik VM aborts and Fennec dies sometimes after Fennec and Android device are idle
    • bug 750965 - crash in libdvm with continuous reloading page after a while
  • Nightly top crashes
    • bug 752428 - crash in nsDOMWindowUtils::SetDisplayPortForElement
    • bug 752426- crash in mozilla::AndroidBridge::TakeScreenshot
    • bug 737128 - mozilla::gl::GLContextEGL::ReleaseSurface GL crash on Droid X
  • note: Nightly could be inflated due to QA testers testing and trying to get repro steps; also takes a while for a fix to have a crash fall off the chart.
  • Reminder: please update your builds to help show impacts of crash fixes

See Mobile Meeting for Mobile specific Socorro updates

Roundtable