Firefox 4.0.1 advertised major update

Fennec 4.0.x

Firefox 5 (Desktop)

Need to verify that the Firefox 5 Release Tracking list is as complete as possible — the Product Marketing Managers and PR need a solid list ASAP. If you worked on something for Fx5 please check to see if it’s on the list or not, and if it’s not either add it or ping deb.

Firefox 5 (Mobile)

Firefox 6 (Desktop)

Everyone who is working on something for Firefox 6 to make sure it has a Feature Page and to make sure it gets added to the Release Tracking page. If you have any questions, ping deb.

Questions and Concerns

(catlee) schedule for final release process?

we need to merge mozilla-beta to mozilla-release and then do another round of build prior to release day.

A: The go/no-go decision for release is around June 7th. If it’s a “go”, we can do the merge to mozilla-release and do builds and QA shortly after that. This gives us plenty of time for testing before release day on the 21st.

(jp) When do beta calls start?

The Beta calls start on Monday May 2nd @2:00pm. We MIGHT change this time and that will be communicated in the meeting reminder send to planning on Friday.

The goals of having a meeting prior to May 17th is basically to help us plan for the cutover and make sure all logistics and issues are getting addressed.

(catlee) when are we pushing to mirrors for 3.5/3.6/4.

A: Planning on pushing in the morning of the 28th, assuming nobody objects. johnath to send mail to r-d

Actions this week

Stuart/Thomas to report back next meeting with a more detailed summary of mobile’s plans for rapid release

ROLLED OVER

Johnath to send note to rel-drivers about 3.5/3.6/4.0 push to mirrors workflow tomorrow

Thunderbird Development

Thunderbird Conversations

Finished work on Thunderbird to speed up loading of messages. Feature work on Thunderbird Conversations (checkout the forward-conversationo branch, a branch with a new menu that allows you to forward a whole conversation). Tidied up the issue tracker by taking advantage of the new GitHub issue tracker.

Roundtable

brendan has expressed concern about the current multi-process plan for Firefox which would break pretty much all extensions that would touch content. bsmedberg has written up Electrolysis/Extension Compatibility and blizzard is organizing a meeting to discuss the options.

Need to verify that the Firefox 5 Release Tracking list is as complete as possible — the Product Marketing Managers and PR need a solid list ASAP. If you worked on something for Fx5 please check to see if it’s on the list or not, and if it’s not either add it or ping deb.

Firefox 5 (Mobile)

Firefox 6 (Desktop)

Everyone who is working on something for Firefox 6 to make sure it has a Feature Page and to make sure it gets added to the Release Tracking page. If you have any questions, ping deb.

Agenda

How about we use whatever rules they are using for Friends of the Tree [1]?

If we do it like “Friends of the Tree” in Mozilla, it’s just the notion that it’s there.

MoMo has been sending T-shirts to those people, but we can’t afford that at this moment.

Action Items

(who needs to do what that hasn’t been recorded in a bug) We should assign people to the open items.

NEW

IanN to email Fallen to get some cooperation for getting a version of Lightning that is compatible with SeaMonkey 2.1 out on AMO.

OPEN

Mnyromyr to coordinate the SeaMonkey response to this years Google Summer of Code.

CLOSED

K.I.V.

Get permission from Google to use their geolocation JSON service [KaiRo]. We can still only wait on the Google front right now. Didn’t hear anything about open Geolocation service yet. No easy solution in sight.

At the “State of the Map – Europe” OpenStreetMap conference, KaiRo will try to get people to team up and create an open service.

kaze has done a ton of work there. We still need to work out some organizational issues. At the moment there is no active interest from MoMo for bringing standalone composer into comm-central. That’s something we (KaiRo and kaze) will have to negotiate with the Thunderbird team (dmose).

Active

A lot of untangling needs to go on between the 3 editors that we have. We can expect a bit of code cleanup for 2.1 but full customization has to go to 2.next as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

KaiRo

Talked through some crash analysis workflows in a CrashKill team meeting to be able to explain those to the Socorro team on the all-hands.

Refined my thoughts on prioritizing work somewhat.

Regularly generated “explosiveness” reports locally and uploaded them, looked at signatures it brought up, filed bugs where needed, commented on others, tried to point some to the right people to get them fixed.

Attended the Mozilla all-hands and discussed a lot of status and planning with a number of people in the CrashKill and Socorro teams as well as other Mozilla employees.

Created wiki pages and filed bugs for some outcomes from all-hands discussions.

Helped the SeaMonkey 2.0.13 release by getting the announcements out the door (bug 644287).

Got the new SeaMonkey 2.1b3 and 2.1pre versions up on crash-stats (bug 647935).

Landed the SeaMonkey patch for installing built-in extensions into the profile (bug 627240).

Did some reviews for SeaMonkey build and release infrastructure.

Got the train rolling again on new build machines for SeaMonkey (bug 572395).

Had some discussions at the all-hands with Standard8, khuey, ted and others on how to go forward on the comm-central build system.

Did some more updates to EarlyBlue and LCARStrek for SeaMonkey 2.1 and, for the latter, some more work to get it to run on Firefox 4.

Cared that L10n dashboard works for SeaMonkey with both the 2.1-targeted “branch” and the development trunk going forward.

mcsmurf

Misak

Mnyromyr

This year’s gSoC proposals for Mozilla as such are very weak in toto, ideas for mail/news related stuff are very scarce — some remotely related seek to improve instant messsaging in Instandbird. SeaMonkey received no student applications.

Any other business?

A week was too long the last time. We don’t have the resources to tie up for a week.

We should limit it to two or three days mid-week. Contiguous days would be better so as not to lose momentum.

Any Triage event is probably feasible only after the Easter Holidays.

tonymec says that around mid-May preferably Wednesday thru Friday would be doable for him. So we have provisionally blocked off 18th-20th May, but we will need to confirm this at next status meeting in a fortnight.

Tentative suggestion: European evenings (20h-24h CEST) three days in a row but we need Aqualon’s feedback as he led the last Triage Event.

Thunderbird Development

Thunderbird Conversations

Important backend work to improve the interaction between Thunderbird Conversations and Thunderbird. bug 648972 will help a lot in this regard. Help badly needed for issue 238, issue 189 and issue 175. More polish work during the week also…

At Mozilla All Hands, discussed the effect on TB Support if TB decides to get on the Firefox rapid release platform train (SUMO support plan for Firefox release plan; we’ll need something similar if TB goes for rapid release)