« previous week | index | next week »
Platform Meeting Details
- Tuesday 2013-05-28 - 11:00 am Pacific
- Dial-in: Audio-only conference# 98411
- People with Mozilla phones or softphones please dial x4000 Conf# 98411
- US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 98411
- US/California/Mountain View: +1 650 903 0800, x4000 Conf# 98411
- US/California/San Francisco: +1 415 762 5700, x4000 Conf# 98411
- US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 98411
- CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 98411
- CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 98411
- UK/London: +44 (0)207 855 3000, x4000 Conf# 98411
- FR/Paris: +33 1 84 88 37 37, x4000 Conf# 98411
- 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
- Engineering Vidyo Room / Warp Core / SFO-Boardroom / Tor Commons
- join irc.mozilla.org #planning for back channel
- FF21 post-mortem held today - https://etherpad.mozilla.org/21-0-Post-Mortem
- FF22b3 going to build today/tomorrow, released before the end of the week
- After 6/4, no more speculative fixes. After 6/11, only new critical regressions will see fixes
|Unresolved Aurora 54 Trackers (non-security, not tracked for Beta)||Unresolved Beta 115 Trackers (non-security)|
Future of the platform meeting
As posted to dev-platform (What should be next for the platform meeting?):
The general feeling about the platform meeting seems to be:
- it has some useful content/purpose that we want to maintain
- it has no particular focus and is not optimized for anyone
For 1, the uses that I've heard include (please feel free to add to this list): - opportunity to find owners for stability, orange factor, other bugs - opportunity to present ideas (like moving to Git) to a chunk of engineering - like to know what other teams are up to
Other useful content that has been suggested includes: - content for hackers - engineering paper cuts
For 2, it seems clear that this meeting is broken in its current form. I have heard the following suggestions to maintain the benefits in 1 without the platform meeting: a. set up a regular newsletter or other form to push team status to engineering (easier said than done) b. set up an engineering managers meeting to handle cross team issues that require escalation like finding bug owners (requires buy in from a good number of managers)
Has the platform meeting run it's course? Is it time to retire this staple of the weekly engineering meeting schedule?
- Code Review Session (sjohnson)
- Doc Sprint around WebAPIs on May 31st (David Bruant)
- Using Gecko as a Widget (GeckoView) (mfinkle)
- Feedback on Prompt.jsm (wesj)
- Async prompt service bug 870062
- Refactor to eliminate GeckoApp.mAppContext for bug 867517, Gecko-based WebView
- Past week's OrangeFactor: 5.74 (Previous Week: 6.88).
- Thanks to philor for disabling failure-prone Android tests that were causing frequent suite timeouts.
- Windows iX Slave Top Oranges
- Win7 media test failures discussed last week still unassigned - bug 872748, bug 872760, bug 872788, bug 872996.
- #1 top orange (bug 858377 - Intermittent test_393498.js | false == true) currently unowned. WinXP iX slaves primarily.
- #4 top orange (bug 774689 - Intermittent 632781-verybig.html | image comparison (==), max difference: 255, number of differing pixels: 14400 ) currently unowned. WinXP iX slaves primarily.
- #7 top orange (bug 875194 - Intermittent Android test_video_crossorigin.html | uncaught exception - NS_ERROR_NOT_AVAILABLE: Component is not available at http://mochi.test:8888/tests/content/canvas/test/crossorigin/test_video_crossorigin.html:33) currently unowned.
- 21 intermittent failures fixed in the last week - List - Thanks!.
Mobile Web Compat
- Brian Hackett delayed the analysis of JS scripts until they are Baseline-compiled, which reduces how much memory is used by scripts that are only run a few times. Among other things, this reduces startup memory by 14mb (10%), entirely eliminating a spike in memory usage we saw in the first 30 seconds after startup on AreWeSlimYet.
- Joe Drew and Andreas Gal landed some nice fixes to reduce image memory usage on B2G, which continues to be a concern.
- Read more about these and many other memory improvements in the MemShrink report for weeks 97-98.
- (armenzg) new win7, winXP test machines live in production
- tbpl database update Thursday - no downtime, but just fyi.
- hg upgrade coming 01june - brief downtime, more details in bug 741353