Meeting Notes Meetings notes from the Mozilla community

17-February-2011

Firefox/Gecko Delivery Meeting Minutes: 2011-02-16

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Firefox/Planning/2011-02-16

From MozillaWiki

« previous week | index | next week »

Firefox/Gecko Delivery Meeting Details

  • Wednesdays – 11:00am PST, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Fin du Monde Conference Room
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • irc.mozilla.org #planning for backchannel
  • (the developer meeting takes place on Tuesdays)
REMEMBER

These notes are read by people who weren’t able to attend the meeting. Please make sure to include links and context so they can be understood.

Agenda

  • actions from last week:
  • schedule and progress on upcoming releases
  • review highlights and notices
  • respond to questions and concerns

Action Items

Schedule & Progress on Upcoming Releases

Firefox 4 (Desktop)

Firefox 4 (Mobile)

Firefox 3.6/3.5

Firefox 3.6.14 and 3.5.17

  • Still investigating the startup crash “regression” on 3.6.14 (bug 633869)
  • Looks like it’s caused by frankenbuilds…older dlls and updated exe
  • Not sure if it is a regression, happened before (and on mozilla-central)
  • Investigating if we made it worse with 3.6.14 changes
  • Adobe is pressing for a release due to a public CSRF issue
  • Once we get more data today, deciding proper way forward
    • Option 1: Release what we have for 3.6.14 and 3.5.17
    • Option 2: Release 3.6.13+CSRF fix as 3.6.14 and the current 3.5.17
    • Option 3: Release 3.6.13+CSRF fix as 3.6.14 and 3.5.16+CSRF fix as 3.5.17
  • Seamonkey release is dependent on 3.5.17 and Thunderbird is dependent on 3.6.14

Firefox 3.6.15 and 3.5.18

  • Waiting to send draft schedule until 3.6.14/3.5.17 are resolved

Firefox Sync

Add-on Builder 1.0a9

  • Builder 1.0a8 was release last Thursday and has been very well received by users. I saw an immediate up tick in account linking from AMO and add-on creation through the Builder.
    • Unsolicited-real-life-true-story feedback: “Great, I have it [my add-on] working now. Mozilla also updated the online addon Builder so it’s clear where your data directory is, very nice. Thanks for your help.” – “..the text editor is a LOT better :)”
  • Starting with 1.0a9 there will be a change in the release structure, most notably, the addition of a maintenance release two weeks after the preceding feature release.
  • Still gunning for a beta 1 after release 1.0a10 (two releases away)

Add-on SDK 1.0b3

  • froze today at 11am
  • many bug fixes landed, plus big docs improvements
  • loader and e10s changes missed (loader changes should land early in 1.0b4 cycle; e10s changes still TBD)
  • RC1 scheduled for today
  • release scheduled for next Wednesday, February 23

Input 3.2

  • release date: 2/22
  • lots of refactoring

Input 3.1 is out!

Feedback Summary

  • Since Beta 9, a huge increase in daily comments about memory and CPU usage 507 5857
  • Many people have commented on input the Beta 11 “feels slower” than beta 10
Issue

SUMO

Input

Buglink
Unable to switch search engines/locks up when using search bar

33+4

538 91

bug 631746
Double title bars when first using Firefox b1 Maybe Firebug

72

152

bug 633611
Firefox 4 Beta 11 Slower than Beta 10

651 104

Hotmail Constantly Reloading

[1][2]

3503

bug 627729
Facebook Chat not working

126

Flash-related crashes (fb games, gmail,

1451 1296

Font Rendering on Windows

204

bug 594325 bug 612846 bug 629857
Netflix streaming player doesn’t work OSX

204

was bug 598406
DivX player doesn’t work

35 (302+ overall)

67

Broken Panorama (missing button, changed shortcut)

50+ from: [3][4][5][6]

254

bug 624588
No save & close dialog when closing Firefox w/multiple tabs

40-ish from: [7][8][9][10]

375

caused by bug 592822 bug 550559
Gmail Locks Up

5

204

Highlights / Notices

Questions and Concerns

Press & Public Reactions

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress