SeaMonkey/StatusMeetings/2012-03-06

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 6 March, 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.

Status of the SeaMonkey Buildbot Master and Tree

• Current Issues with existing machines:
  • There are problems with some hosts on parallels, current plan is to build the Parallels VMs on ESX instead once scl3 has network and power to the new ESX cluster.
  • One win VM, switched from FAT32 to NTFS for one of its drives, need to recreate folders appropriately.
• "Where do we stand with the machine(s) right now?"
  • bug 721516 migrate seamonkey systems out of sjc1/scl2 and into scl3/scl1.
    • (2012-02-23)
      • "r4 minis: to be moved to scl3 on the B train 3/12"
      • "r2/r3 minis: to be moved to scl1 on the C train on 3/26"
      • "iX hosts: to be moved to scl3 on the C train on 3/26"
      • "VM's: to be moved to scl3 when ESX is ready"
      • "HP DL120G7's: Matt will follow up with dcops to locate and finish these hosts"
    • + 7(+) blocking bugs.

Release Train

• 2.8b4 was shipped on February 25.

Extensions Compatibility Tracking

We need some help with the add-ons listed under the "2.0x" heading. Anything above it will work out of the box with SM 2.7 and later (yay to compatible-by-default!). Perhaps Ratty can go through his xSidebar site and check which add-ons are not compatible with at least SM 2.1 - that would help, too.

• Since xSidebar itself is not compatible with any recent SM version, it should not be listed as a featured add-on on AMO. Who can make that change?
  • KaiRo said he did, but it's still featured for at least en-US and de locales.
  • If anyone wants to suggest add-ons to be featured, send them to InvisibleSmiley (in manageable doses that is).

• Addon Compatibility Listings, mostly maintained by InvisibleSmiley
  • Recent changes can be found here.
  • Restructured for compatible-by-default.
• Enigmail provides versions for release (AMO) and all branches (Enigmail nightly page). The current release is compatible with both 2.6 and 2.7.
• Lightning provides versions for the current stable and beta releases (AMO) and nightlies for trunk and Aurora (Calendar Versions page). Lightning 1.3b2 which works with SM 2.8bX is available from AMO (Development Channel).
• Firebug is compatible but not flagged as such on AMO (depends on automatic tests being set up and run on the Firebug side: bug 680837, needs a Python coder). Stable Firebug version 1.9.x works with any recent SM version. FB 1.10a4 works with trunk again, though it eats some shortcuts (Issue 5285).
• 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
• The SeaMonkey Features page links to sub-pages for all recent SM versions, including those in development. Please help InvisibleSmiley add major features to the respective pages, ideally as they land. These pages are used when creating release notes, so the more up-to-date the better.
• bug 666303 (Seamonkey 2.1 is detected as Firefox 2.1 on the Add-on Site) and bug 671085 Confusing compatibility error when visiting Firefox listing page using SeaMonkey)
  • We don't have a dedicated person here who understands how AMO really works, who to contact in order to actually get things moving etc. Unfortunately. Someone needs to sit down and find the offending logic, wherever it may be (probably in the AMO source, at github).

2.x (Last, Current, Next)

• 2.7 had ~x ADU by last Thursday and 2.7.1 has had ~y and 2.7.2 has had ~z downloads so far.
  • Of the released versions, as of last Thursday, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4, D% on 2.5, E% on 2.6 and F% on 2.7. So, in the last two weeks, ~Gk (an additional H% of ADU) have migrated to 2.6 or above.
• Still a large, but slowly decreasing, chunk of users on 2.0.x.
• Figure out what is preventing people from moving from 2.0.x to the latest versions.
  • Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.)
  • Perhaps putting resources into getting certain extensions working with SM 2.4 and above (those that won't work with SM 2.7 automatically due to compatible-by-default extensions).
  • 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.
  • Are some Linux distributions are still stuck on 2.0? We have data on OSes and OS versions in the raw data in the Mozilla metrics, AFAIK, Callek now also has access to that.

Usual reminders:

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

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

• One tracked 2.5 issue still open.
  • 2.1 through 2.7 have NOT included the ka locale. The last release with ka locale shipped was 2.0.14 and the ka l10n maintainers have not yet updated for changes in later SeaMonkey versions.
  • Callek now needs to morph bug 667147 into removing |ka| from our [current] automation entirely (all-locales). Callek will look at best locale to transition any ka users to.
    • Plan is to migrate ka users to en-US with a english dialog saying they are out of date, and a link to the all-locales page if there is a language they understand better. Current ADU of ka alone is 3-5 individuals, so low impact.~Callek
• The New 2.7 Features page has a comprehensive list of features.

2.Next

• InvisibleSmiley created a restartless add-on (available on AMO) for SM 2.8 (now in Beta) which adds an "Add-ons" options to the list of engines on the Sync pref panel.
• Remember to help update the New Features pages as we go along.

Feature List, Planning

Bug statistics for last two (full) weeks: 51 new, 27 fixed, 32 triaged.

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

Open reviews/flags: 29 review 9 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.10 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 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.
  • The standalone Composer patch has to be rebased and fixed for MacOSX.
  • Kaze is considering moving Kompozer to an addon so that we can reuse the dialog boxes but start fresh for the content part. Also we can then use the current devtools. KaiRo told kaze in Berlin it seemed a good idea, as it could allow to run a Composer *tab* instead of a Composer window.
  • Kaze working on it on his spare time, with an Indian contributor.
  • 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. Otherwise stalled. :-(

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

InvisibleSmiley

• Fixed:
  • bug 711334 Be explicit that TLS version is 1.0
  • TODO

• ToDo:
  • bug 701714 Add support for DOM full-screen
  • bug 640420 Add draggable splitter between urlbar and searchbar
  • look into
    • bug 698038 Update Preferences help for the new section to control crash report
    • bug 696757 Port "Time range to clear" from Firefox to SeaMonkey's "Clear private data" dialog
  • track
    • bug 687316 (Remaining) Sync changes to port to Suite

Any other business?

• Need to review project areas
  • IanN has put out a final version of the project areas list, and will hopefully be updating the wiki this weekend.
  • IanN opened bug 732698 for updating the project website.
  • We will 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. We're unlikely to move to ESR until Gecko 10.0.1 or 10.0.2.
  • 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 is 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.