Confirmed users, Bureaucrats and Sysops emeriti
3,599
edits
Firefox/Planning/2010-06-02: Difference between revisions
m
moved Firefox/DeliveryMeetings/2010-06-02 to Firefox/Planning/2010-06-02
| (12 intermediate revisions by 4 users not shown) | |||
| Line 64: | Line 64: | ||
== 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> | ||
* {{bug|524223}} has finally landed for 3.6.5/3.5. | * {{bug|524223}} has finally landed for 3.6.5/3.5.11 - needs dev docs and outreach (see also {{bug|536606}}) (zwol) | ||
** back-ported version is slightly different than trunk version | |||
** thus the need for web-evang! | |||
* Fennec 2.0 is looking to create an alpha off of mozilla-central, trying to figure out when and whether or not they do this off trunk or mozilla-1.9.3 | * Fennec 2.0 is looking to create an alpha off of mozilla-central, trying to figure out when and whether or not they do this off trunk or mozilla-1.9.3 | ||
** will lock down a plan when we're closer to the time | |||
** ideally would work off mozilla-1.9.3 if timing works out | |||
== Questions and Concerns == | == Questions and Concerns == | ||
| Line 71: | Line 75: | ||
* Question for people with Firefox connecting to sites slowly: Is Firefox "Allowed" in Windows Firewall? (cww) | * Question for people with Firefox connecting to sites slowly: Is Firefox "Allowed" in Windows Firewall? (cww) | ||
** not sure why Firefox is slow but not blocked | |||
** something to investigate if we hear people saying that Firefox is really slow | |||
* what is the cost of shipping Firefox 3.6.4 in terms of delaying shipment of other security and stability bugs? (abillings) | * what is the cost of shipping Firefox 3.6.4 in terms of delaying shipment of other security and stability bugs? (abillings) | ||
** can we think about landing some of the newer security bugs in additional builds, or would that cause more problems than it is worth? | |||
** less to do with security backlog, and more to do with approval backlog | |||
** think our current strategy is still virtuous, OOPP is a significant win | |||
* what is the cost of shipping Firefox 3.5.10 before Firefox 3.6.4? (beltzner) | * what is the cost of shipping Firefox 3.5.10 before Firefox 3.6.4? (beltzner) | ||
** potential risk with people reverse engineering an exploit | |||
** that risk already exists | |||
** would mean not opening up some CVEs | |||
** consensus seems to be "yes, we should do it." | |||
* have we swept through all the plugin/ipc bugs to know size and scope of remaining OOPP risks? (beltzner) | * have we swept through all the plugin/ipc bugs to know size and scope of remaining OOPP risks? (beltzner) | ||
** bsmedberg says that this happened on the last bug day | ** bsmedberg says that this happened on the last bug day | ||
** action item: '''clegnitto''' says that he'll take another pass through | ** action item: '''clegnitto''' says that he'll take another pass through before another "go to build" | ||
* Turning off FF3.0.x machines | |||
== Press & Public Reactions == | == Press & Public Reactions == | ||
| Line 96: | Line 111: | ||
** beltzner to keep digging into 64-bit issues (OSX as x86_64 only? etc) | ** beltzner to keep digging into 64-bit issues (OSX as x86_64 only? etc) | ||
** axel to start getting on l10n-merge | ** axel to start getting on l10n-merge | ||
*** {{bug|568298}} filed, resolve on releng | |||
* review highlights and notices | * review highlights and notices | ||
* respond to questions and concerns | * respond to questions and concerns | ||
| Line 113: | Line 129: | ||
<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 a branch plan for mozilla-1.9.3? (beltzner) | * do we have a branch plan for mozilla-1.9.3? (beltzner) | ||
** RelEng aiming for mozilla-1.9.3 branch to be online by end of next week (Friday 11th June) | |||
** reminder that this will mean branch landings of trunk code! | |||
* once we have the mozilla-1.9.3 branch do we want to use it immediately, or wait until some point during the beta cycle? | |||
** bsmedberg thinks it will help us focus | |||
** stuart is worried about the additional overhead | |||
** beltzner wanted to avoid adding restrictions to mozilla-central | |||
** dveditz doesn't think we should branch until we have to do so | |||
** might want to wait until the end of the month | |||
** axel concerned that not having a 1.9.3 branch means he can't do localization code the way he'd like to | |||
** action item: '''stuart''' to gather branch stakeholders and come up with a proposal | |||