Firefox/Planning/2010-06-09: Difference between revisions

 
(22 intermediate revisions by 10 users not shown)
Line 1: Line 1:
<small>[[Firefox/DeliveryMeetings/2010-06-02|&laquo; previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/DeliveryMeetings/2010-06-15|next week &raquo;]]</small>
<small>[[Firefox/DeliveryMeetings/2010-06-02|&laquo; previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/DeliveryMeetings/2010-06-16|next week &raquo;]]</small>


'''Firefox/Gecko Delivery Meeting Details'''
'''Firefox/Gecko Delivery Meeting Details'''
Line 17: Line 17:
* review highlights and notices
* review highlights and notices
* respond to questions and concerns
* respond to questions and concerns
'''Action Items'''
* christian to work with chofmann and socorro team to investigate crash rate spike
* erica and mayumi to finalize comms plan with beltzner
* QA to test with new Flash and new Silverlight


== Schedule &amp; Progress  ==
== Schedule &amp; Progress  ==


'''[[Releases/Firefox 3.5.10|Firefox 3.5.10]]''' / '''[[Releases/Firefox 3.6.4|Firefox 3.6.4]]'''
'''[[Releases/Firefox 3.5.10|Firefox 3.5.10]]''' / '''[[Releases/Firefox 3.6.4|Firefox 3.6.4]]'''
* Doing an update that only updates channel prefs, moving 3.6.4 users on the release channel over to the beta channel. Going out now
* '''We think OOPP is ready''' - anyone disagree?
** New issues have slowed
** 522,309 build #6 users on Windows, still climbing. This is very good.
** QA worked through [http://etherpad.mozilla.com:9000/video-sites this list of video and game sites] to make sure we have testing coverage on popular sites that use plugins. The list was crowdsourced after all call to create it on Twitter by beltzner
* Decided to keep 3.5.10 tied to 3.6.4 to make Linux vendor's lives easier
** Argument for decoupling decision was made based on potential issues, whereas the negative effects on Linux vendors are known and quantifiable
* Shipping schedule needs to be talked about
** Still investigating the [https://bugzilla.mozilla.org/show_bug.cgi?id=569104 Cnet bug] and [https://bugzilla.mozilla.org/show_bug.cgi?id=562198 bug 562198]


'''[[Releases/Firefox 3.5.11|Firefox 3.5.11]]''' / '''[[Releases/Firefox 3.6.5|Firefox 3.6.5]]'''
'''[[Releases/Firefox 3.5.11|Firefox 3.5.11]]''' / '''[[Releases/Firefox 3.6.6|Firefox 3.6.6]]'''
* 1.9.2.5 was used by Fennec, so next platform version is 1.9.2.6. We will keep the version #'s coherent by naming it Firefox 3.6.6
* I will be moving the blocking flags and status flags as appropriate
* If you have approvals for 1.9.2.5 they are now for 1.9.2.6
* If we need a chemspill for 3.6.4, this will be off the 3.6.4 relbranch
* If no chemspill, planning early-to mid July, making sure to have this out before BlackHat in late July
* WebM discussion will likely happen shortly


'''[[Releases/Firefox 3.7a5|Firefox 3.7 Alpha 5]]'''
'''[[Releases/Firefox 3.7a5|Mozilla 1.9.3 Developer Preview 5]]'''
* trunk is now feature complete
* just need to get QA signoff and prepare release notes
* QA wants to talk about requirements for ship


'''[[Mobile/Fennec/Fennec1.1|Fennec 1.1 RC]]'''  
'''[[Mobile/Fennec/Fennec1.1|Fennec 1.1 RC]]'''  
Line 45: Line 67:
== Highlights / Notices ==
== Highlights / Notices ==
<small>''Please add notes for issues you'd like to bring to everyone's attention!''</small>
<small>''Please add notes for issues you'd like to bring to everyone's attention!''</small>
* Build will be generating Linux64 and OSX 10.6 64-bit builds for the first time as part of a release.
* Build
** Mozilla 1.9.3 Developer Preview 5 will have Linux64 and OSX 10.6 64-bit builds for the first time as part of a release.
** 3.6.4build6 users will be updated to beta channel {{bug|570797}}
** Assuming FF3.5.10 ships Tuesday, RelEng will be powering off FF3.0.x machines before this meeting next week. Details in {{bug|554226}}


== Questions and Concerns ==
== Questions and Concerns ==
<small>''Please add any questions or concerns you would like discussed at today's meeting.''</small>
<small>''Please add any questions or concerns you would like discussed at today's meeting.''</small>
*Should {{Bug|570774}} block the Alpha 5 release?
** don't think so, not even sure that it should block a beta - secondary UI on a single platform
** does look like there's a fix for this in {{bug|565392}}
*QA Testing Requirements for Alpha 5
** https://wiki.mozilla.org/Releases/Firefox_3.7a5/Test_Plan#Focus_Areas
** Good number of changes have landed since Alpha 4. Would like to spend some more time with the builds in light of this fact.
** Getting builds tomorrow and and having 1/2 day to test might not be realistic.
** beltzner thinks that there might be some difference of opinion about required quality bar for developer previews
** beltzner and mevans to follow up offline and figure something out


== Press & Public Reactions ==
== Press & Public Reactions ==
*[http://arstechnica.com/open-source/news/2010/06/mozilla-to-weave-sync-features-into-next-version-of-firefox.ars Mozilla to weave sync features into next version of Firefox]
*[http://download.cnet.com/8301-2007_4-20006515-12.html As Mozilla readies latest browser, Weave becomes Firefox Sync]
*[http://www.h-online.com/open/news/item/Mozilla-delays-Firefox-3-6-4-1014319.html Mozilla delays Firefox 3.6.4]
*[http://lifehacker.com/5553403/firefox-364-release-candidate-stabilizes-flash-and-other-plug+ins?skyline=true&s=i Firefox 3.6.4 Release Candidate Stabilizes Flash and Other Plug-Ins]
*[http://www.theregister.co.uk/2010/06/02/firefox_3_6_4_release_candidate/ Hesitant Mozilla nurses Firefox 3.6.4 baby for a bit longer]
*[http://www.wired.com/epicenter/2010/06/latest-firefox-release-isolates-flash-for-a-more-stable-browser/#ixzz0qNZKXwnV Latest Firefox Release Isolates Flash for a More Stable Browser]
= '''<big>Future Releases: Planning & Co-ordination</big>''' =
= '''<big>Future Releases: Planning & Co-ordination</big>''' =
'''Agenda'''
'''Agenda'''
Line 63: Line 108:
== Highlights / Notices  ==
== Highlights / Notices  ==


<small>''Please add notes for issues you'd like to bring to everyone's attention!''</small>
* XPCOM registration is changing significantly and in a breaking way, bug 568691. This may mean that we are going to bump the gecko version to 2 for this release. bsmedberg will post more details to md.planning... today? All extensions that use XPCOM components (which is many of them) will need to be updated.


== Questions and Concerns ==
== Questions and Concerns ==
<small>''Please add any questions or concerns you would like discussed at today's meeting.''</small>
<small>''Please add any questions or concerns you would like discussed at today's meeting.''</small>
* do we have OOPPsie reports for OSX yet? (marcia)
** true, not difficult to do, but to be done by same people on retained layers critical path
** need to decide if we can ship first beta without it
* l10n for Firefox 4 Beta 1?
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits