SeaMonkey/StatusMeetings/2012-01-10

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 10 January, 2012, 13:00 UTC
• Location: #seamonkey IRC channel

Agenda

• Who's taking minutes? -> TBD
• Nominees for Friends of the Fish Tank?
  • Please note A person or entity can't be nominated twice in a row.

Action Items

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

NEW

OPEN

• IanN to write the "Friends of the Fish Tank" F.A.Q.

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

• "Where do we stand with the machine(s) right now?"
  • bug 702490 (Rack 2 - 1U mac mini chassis(4 Mini's) in SCL2 for SeaMonkey).
    • These won't be racked until emux can get power situated at SCL2.
• The SeaMonkey tree is missing the some build boxes.
  • We still need to bring up the linux 32 boxes we had, but it's progressing. (had to fight fires with the newly brought up win boxes, but all should be good now)
• The tree status is currently OPEN and un-METERED.

Release Train

• Get comm-aurora and comm-beta on MXR (bug 653424).
  • Jake Maul [:jakem] from Server Ops has taken over the bug from Callek.
• 2.7b3 shipped January 7.
• The next six-weekly merge will be on December 31.
• en-GB patches needs review. Check to see if a blanket approval to land. (IanN)

Extensions Compatibility Tracking

• Addon Compatibility Listings created and maintained by InvisibleSmiley, with help from some community members like DERoss.
  • Recent changes can be found here.
  • ACR 1.0.2 breaks AOM search when used with trunk, Aurora or Beta (bug 715493)
• Enigmail provides versions for release (AMO) and all branches (Enigmail nightly page). The current release is compatible with both 2.5 and 2.6.
• Lightning provides versions for the current stable and beta releases (AMO) and nightlies for trunk and Aurora (Calendar Versions page). There has been some confusion about versions for Beta. The link on the Calendar Versions page points to tinderbox builds which are auto-removed after some time. Over the Christmas period, no Beta builds were available from both the Calendar Versions page and AMO. Lightning 1.2b1 is available from AMO now (Development Channel) and should be available in time for future betas.
• The latest Firebug is now fully compatible but still not flagged as such on AMO (which seems to depend on automatic tests being set up and run on the Firebug side, see Issue 4430). Use Firebug 1.9 for 2.4 and later (maybe even earlier SM versions).
• Besides the above, we should also take a look at other add-ons that are important for our users when they switch to 2.x.
  • Useful query: https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular
• KaiRo created a SeaMonkey Features page and sub-pages for all those that are in development. Please add major features to the respective pages, ideally as they land.

2.x (Last, Current, Next)

• 2.5 had ~x ADU by last Thursday and 2.5 has had ~y downloads so far.
  • Of the released versions, as of last Thursday, we have a% on 2.0, b% on 2.1, c% on 2.2, d% on 2.3, e% on 2.4 and f% on 2.5. So, in the last four weeks, ~gk (an additional h% of ADU) have migrated to 2.4 or above.
• Figure out what is preventing people from moving from 2.0.x to the latest versions.
  • Perhaps putting resources into getting certain extensions working with SM 2.4 and above.
  • Still need volunteers to look at what is keeping people at below 2.4. IanN could try knocking something up and send it round members lists for polishing but he's not on all the channels (mozillazine, etc) to post it to when finished.
    • 2.5 introduced a news server problem which is still present in 2.6 and 2.7 pre-releases (bug 695309; jcranmer is on it) which explains why some people stay on 2.4 (but not why others stay below that one).
• Please make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when we to do a release we can be sure that we don't miss anything.
  • Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.
  • Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.

2.6

open tracking (0) tracking requests (0) targeted (0) fixed (40)

• One tracked 2.5 issue still open. If not resolved or no response by then, Callek plans to morph this into removing |ka| from our [current] automation entirely (all-locales). update?
• The New 2.6 Features page has a comprehensive list of features.

2.Next

• Remember to help update the New Features pages as we go along.

Feature List, Planning

Bug statistics for last two (full) weeks: 45 new, 15 fixed, 50 triaged.

• Good triaging effort! :-)
• Good further triage targets could come out of looking at the component bug counts, pick yours!

Open reviews/flags: 34 review 16 super-review 0 ui-review 6 feedback

Major wanted/needed features:

Active

• bug 606683 Allow customization of toolbar in Composer and MailNews Composition [IanN].
  • Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.
  • IanN will need to poke some people about reviews not happening quickly enough.
  • IanN is still wading through the unpicking of Composer/Mail Compose code in the dependent bugs. After that he will be reworking his customising patches.
• bug 477845 Build a standalone (Comm-central) Composer. [kaze]
  • kaze has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.
  • IanN was supposed to help get builds working with --enable-tests.
    • Will look into this once he gets his customization patches reworked.
• Real full-screen (bug 610509) and DOM full-screen (bug 701714)
  • patches provided by Mnyromyr and InvisibleSmiley.

Needing help, Unowned, Stalled

• Kill-RDF:
  • bug 657607 Port jminta's kill-rdf to SeaMonkey where applicable Part 2 [meta].
  • bug 657604 Remove the RDF global object. [serge]
• bug 436794 Enable Mac OS X system address book per default and add UI.
  • SM UI needed, unowned, helpwanted.
• bug 449728 Drag tabs between windows.
• bug 477840 Backport KompoZer to Composer (Depends on bug 477845).
  • 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 (Standard8).
• bug 507841 Port Bug 422814 - Make account configuration quick, easy, and more secure (autoconfig, Quick Account Setup).
• bug 533908 SeaMonkey Mail: tabs not restored [misak].
• bug 523274 Complete new default theme icon set.
  • A list of TODO icons is up in the bug.
• bug 526210 Update the icon set for the SeaMonkey Modern Theme.
  • bug 548778 New communicator icons (based on Strata theme) for SeaMonkey. Some proposed icons got posted, we should take a look how to get that contribution into the product.
  • The rest is unowned so far.
• bug 87098 [SeaMonkey] Delete key should delete location bar history list entry.
  • Note: Our location bar history doesn't and can't use autocomplete at all.
• bug 677484 Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.
• bug 654009 Reply to list: automatically determine From: address
  • Note: The actual task here is to port bug 45715 "Reply to List" [button/(context) menu item]
• bug 664309 Make the built-in ChatZilla display a cZ icon in SeaMonkey (now helpwanted)

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).

Any other business?

• Need to review project areas
  • IanN has put out a final draft of the project areas list, and will then confirm that anyone who is not in the loop already has been consulted.
    • There are two items that need answering still in the areas. IanN will remind people about what still needs answering.
  • in the end, we also need to update the Mozilla-wide list of official reviewers
• Extended Support Releases (ESR)
  • At the moment looks like that will be based off Gecko 10 so that will be 2.7 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.7.
  • Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.
  • An ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer what MoCo's general plans for their marketing/target/support levels etc. are.
  • mcsmurf is on the ESR mailing list and has volunteered to be our ESR goto guy.
• Geolocation
  • Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central.
  • For comm-beta all we need to do is (bug 494421) to add pref("geo.wifi.uri", "https://www.google.com/loc/json"); to browser-prefs.js. However we're not even sure we are legally allowed to ship with the URL in, we might need to actually put in a pref to disable that in newer builds.