Firefox/Planning/2011-04-13

From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

Firefox/Gecko Delivery Meeting Details

  • Wednesdays - 11:00am PDT, 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.

FORCETOC

Actions from Last Week

(none)

Schedule & Progress on Upcoming Releases

Firefox 3.6.x/3.5.x/4.0.x

  • "go to build" FF3.5.19, FF3.6.17, FF4.0.1 on 13apr2011
  • release FF3.5.19, FF3.6.17, FF4.0.1 on 26apr2011

Firefox 4.0.1 advertised major update

  • are we clear on criteria to do this? risks/issues?

Fennec 4.0.x

  • expecting "go to build" Fennec 4.0.1 this week.

Firefox 5 (Desktop)

Firefox 5 (Mobile)

Firefox Sync

Add-on Builder 0.9.3

  • Release is on-track
    • Search phase 1 is almost landed!
    • HUGE improvements to the editor, HUGE.
  • The next release will include the stand-alone add-on repacking service that will both increase test speed in the Builder's editor and allow for AMO to batch repack add-ons for new releases of the SDK & Firefox.

Add-on SDK 1.0b5

  • timeline:
      • Freeze: Wednesday, April 27 @ 11am PT
      • RC1: Wednesday, April 27
      • Final: Wednesday, May 4
  • this will be the last 1.0 beta
  • focus is on polishing existing functionality in preparation for stable release

Input 3.4

  • Release Firefox Input 3.3.5 to support the new channels process
    • Band-aid to accept all feedback as happy/sad/idea across any build. Test Pilot team has updated their code and it has landed for Aurora.
    • We're going to follow-up with weekly iterative releases that round out this approach
      • Remove the release dashboard and uplift the beta dashboard to the general one
      • Update submission forms on desktop and mobile

Feedback Summary

  • Working on a feedback strategy to support the new channels process. The plan, thus far and going forward, can be found on our central wiki

Press & Public Reactions

Questions and Concerns

  • Discuss how to communicate / track changes for our short releases. (blizzard)
  • What does the update experience feel like? (mayumi)
  • EndOfLife of 3.5/3.6? (catlee)
  • Requirement to recompile binary components in addons per release is creating a little heartburn with developers who use them. I want to ensure that promotion of JS-ctypes is the recommended approach, and need to know where devs with questions should be directed. (kev)

Actions this week

  • Christian: come back with confirmed schedules for 3.5.19, 3.6.17 and 4.0.1, as well as target date for advertised major update from 3.x to 4.0.1
  • Jay: Make sure Christian gets a bug number on slow add-on discovery pane in Asia bug 635610
    • DONE
  • Stuart/Thomas to report back next meeting with a more detailed summary of mobile's plans for rapid release
  • Laura/Mayumi to poke metrics about getting nightly reports to include aurora stats (or get them to attend :)
  • Aakash/Cheng to come back with preliminary aurora feedback for next week, albeit sparse while they build a new feedback plan