From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details


  • Who's taking minutes? -> mcsmurf
  • Nominees for Friends of the Fish Tank:
    • Neil for tireless patch reviewing
    • xabolcs for working on Bug 848265 (ChatZilla)

Action Items

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


  • Need to reward the nominees of the freinds of the fish tank from this year!



Status of the SeaMonkey Buildbot Master and Tree

  • Tinderbox is going to be EOLed. We need to move the SeaMonkey tinderboxpushlog off. See:
    • bug 843356 [Tracking bug] remove SeaMonkey dependency on
    • Mostly done now, just a few loose ends.
  • Intermittent issue with Mac OSX64 Debug Leak log comprehension. Issue tracked in bug 774844. Also see possibly related Thunderbird bug 806492..
  • Two remaining machines on Parallels are the buildmaster (cb-seamonkey-linuxmaster-01) and Linux64 (cb-seamonkey-linux64-01). These need to be migrated to ESX. Specifically:
    • sea-vm-linux64-1 will replace cb-seamonkey-linux64-01 (and is ready to go)
    • sea-master1 will replace the current buildmaster.
  • bug 740633 set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed.
    • Awaiting puppetmaster fully prepared to instantiate as Linux Mock-Based slaves
  • sea-puppet (one of said hp machines) is ready to be configured as a puppet master (bug 827079), needs audit of the manifests and settings creation.
  • comm-* will be building out of mozilla-* eventually. Jcrammer is working on this.

Fixed Stuff Since Last Meeting

  • SeaMonkey BuildAPI is now setup and running internally, investigating if it can be externally accessed.
  • Windows platform builds were broken by (bug 842341). bug 842445 migrated our Win builders to use pymake by default.

Release Train

  • SeaMonkey 2.17 Beta 4 shipped March 28.
  • SeaMonkey 2.17 will ship later today April 2.
  • SeaMonkey 2.18beta1 will build/ship this week, likely ship Friday April 5.

Too many betas:

  • mcsmurf/IanN think that we can reduce the number to three or four. Mail has been sent to seamonkey-members to discuss this.
  • Ewong says there is normally 1 beta per week.
  • Callek to drive this conversation to a final outcome until today.
    • Callek still hasn't done this yet, he should be nudged punished :-) .
  • New number of betas: Best idea is probably beta 1,3,maybe 5,6 (compared to the previous number six betas per release cycle)

Extensions Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • There are now Lightning versions for both SM 2.16.x (Lightning 2.1b1) and SM 2.17 betas (Lightning 2.2b1) available on AMO.
  • Shipped extensions (DOMI, CZ, Venkman) compatibility:
    • Extensions are now compatible by default thus mitigating the issue. Although some people still disable c-b-d and run into issues.
  • Our build team (Callek, ewong, Serge) needs to automate DOMI branch selection rather than having to tweak the every 6 weeks. bug 763506
    • In the past Serge often pushed this forward for us. But with Serge on a sabbatical, Ewong thinks he should talk to Callek in getting this automated.
    • For 2.16, compatibility bumps were done as outlined in bug 808426.
  • There was some discussion about what ChatZilla version will be shipped in SeaMonkey 2.18
    • SeaMonkey tries to ship the current release branch of an extension (like CZ) on Aurora branch date
    • Shipping non-released versions will break update check with AMO
    • SeaMonkey 2.18 will ship ChatZilla 0.9.90

2.x (Last, Current, Next)

  • [From last meeting:] There is a problem with the metrics server, so no current data is available
    • Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.). This even more applies to 2.10 which dropped support for Win2k and WinXP without SP2, and 2.14 dropping Mac OS X 10.5 support.
    • We now have a webpage for latest builds available for "Legacy Platforms" like PPC (bug 759315)
  • See Basics page for the usual reminders.


open tracking (0) tracking requests (4) targeted (0) fixed (5)


  • Current breakages:
    • Nothing significant at the moment.
  • Mozilla-central bugs that affect us:
    • Note: Please file bugs if you notice any landing on mozilla-central that might break us. Please don't depend on Ratty noticing such landings.
    • bug 769764 move proxy resolution to separate thread and remove sync api. Tracked in:
      • MailNews bug 791645 Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
    • bug 737615 Remove use of synchronous cache API from unit tests. Tracked in:
      • bug 804972 Remove synchronous calls to nsICacheSession::openCacheEntry in SeaMonkey tests.
      • Mcsmurf says this is almost fixed but there was a test failure. He will close this bug and open a new one for the failure.
    • bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
      • bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
      • bug 794772 Port |Bug 713802 - Build with GIO support (and drop GnomeVFS)|. This is dependent on bug 795354.
    • bug 795144 default --disable-gnomeui icon theme support
      • porting bug needed for the two changesets? Changes could be folded into bug 794772 above.
      • IanN says he will look into these issues. Ewong is also working on bug 794772.
    • bug 834457 Remove deprecated synchronous APIs from Places. Tracked in:
      • bug 834498 Remove usage of setPageTitle and isVisited from Seamonkey's tests. Mcsmurf is making good progress.
    • bug 839034 move markPageAsXXX methods to nsINavHistoryService. Tracked in:

Feature List, Planning

Private Browsing is now mostly complete. However parts of it have been uplifted to 2.18, so we have some options:

  • Uplift all the patches from 2.19/2.20 to 2.18
  • Remove UI for Private Browsing from 2.18 and decide whether to leave it in for 2.19 in six weeks
  • Remove UI for Private Browsing from 2.18 and uplift any remaining patches from 2.20 (e.g. bug 856406) to 2.19

Also we need to figure out if we want a new about:privatebrowsing page which someone will have to write. Also I don't know whether we have any help content yet.

Bug statistics for the last two (full) weeks: 26 new, 22 fixed, 21 triaged.

  • Medium triaging effort.

Open reviews/flags: 25 review 8 super-review 1 ui-review 8 feedback

  • bug 847546 Support Retina Display (HiDPI) on SeaMokney on MacOS X.
    • Ratty thinks we will need 2x PNGs as well as other changes. See Core Tracking bug 785330 for supporting HiDPI mode (Retina Display) on Mac OS X.
  • See Feature List page for major wanted/needed features.
    • Ratty suggests featuring one or more bugs from that page at each meeting.
  • Featured helpwanted bugs:
    • bug 677484 Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.

Good First Bugs

  • Note: The GFB list is open to all including our regular contributors.
  • Ratty is working on an updated GFB list, suggestions welcome.
  • New GFBs recently added:
  • Currently there are 24 GFBs open, 2 are being actively worked on. bug 735333 needs some help getting this running on the try-server. Mcsmurf is assisting.
  • List of Open mentored bugs.
    • Ratty notes that there are 23 bugs that are GFBs but without the mentor keyword. These need to be audited to see if they are really suitable as GFBs.
  • In the last two weeks since the previous meeting:
    • bug 735333 Use Services.prefs instead of preferences-service / gPrefService, in SeaMonkey code. Mcsmurf will check in the Services.prefs patches soon. IanN says that once this is done, it's worth asking people who use trunk to give those areas a good test, because we have regressed before with Services.jsm landings.
      • Mcsmurf did some testing on this, but need to check how to "discover" JS bugs, as they don't generate TEST-UNEXPECTED-FAIL in the log.
    • bug 752331 Atul had to give up on this bug due to illness. Ratty will leave this open for the time being.
  • Mentors of stalled bugs should try to communicate with the assignees and if they can't work on them any more to unassign/free up those bugs.

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




  • bug 848222 Use treestatus for SeaMonkey tree closures.
  • bug 852841 Add SeaMonkey 2.17 Beta 3 to bouncer.
  • bug 854290 Update SeaMonkey website for 2.17 Beta 3.
  • bug 855164 Add SeaMonkey 2.17 Beta 4 to bouncer.
  • bug 855967 Update SeaMonkey website for 2.17 Beta 4.
  • bug 855997 Add SeaMonkey 2.17 to bouncer.

Working on:

  • bug 740633 set up seamonkey HPs in scl3.
  • bug 817383 SeaMonkey needs new (public) GPG key, in order to support signing releases properly.
  • bug 827079 Setup SeaMonkey PuppetMaster.
  • bug 827178 Update stage.m.o cron to match recent changes with ffxbld cron.
  • bug 845844 Deploy updated tbpl to



  • Fixed:
    • bug 624432 - Port |Bug 337964 - changing account during message composing doesn't apply signing prefs from new account| to SeaMonkey
    • bug 846752 - Port Bug 713846 (unified log handling) to SeaMonkey Buildbot, utilize statusDB
    • bug 847257 - Update Help for changes from Bug 624432.
    • bug 856953 - SeaMonkey-beta must have enable_pymake set.
  • Review:
    • bug 739056 - Port |Bug 715099 - Convert nsProfileMigrator to JS so we can use JS modules on migration| to SeaMonkey

  • Working On:
    • bug 633937 - Port bug 562048 to suite.
    • bug 813844 - Port changes from Bug 718067 and changes from Bug 808219 (Firefox Health Reporter service)
    • bug 834690 - Port |Bug 569342 - Find bar should not be enabled in about:addons| to SeaMonkey
    • bug 834691 - Port |Bug 632233| to SeaMonkey (XULBrowserWindow.onLocationChange looks for a "disablefastfind" attribute in all content documents before ruling them out)
    • bug 837649 - [Tracking Bug] Stop OSX 10.5 support for SeaMonkey project
    • bug 837650 - Stop support for OSX 10.5 in suite/ tree


  • Some testing, reviewing and commenting.
  • Fixed:
  • Checked in pending review:
  • Waiting for review:
    • bug 808835 Add l10n.ini file for Chatzilla
    • bug 837408 Add en-GB locale to gaia
    • bug 786316 Save As Template should correctly manage multiple selections
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
    • bug 778534 Use image instead of html:img in instant messaging
  • Reviewed and waiting for feedback from mobile peer:
  • Working on:
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with --enable-tests.


  • Fixed:
    • bug 852261 Update SeaMonkey website for 2.17 Beta 2



  • Fixed bug 856587 [SeaMonkey] test_contextmenu.html | checking item #4 (---) name - got context-openlinkinprivatewindow, expected ---
  • Worked on bug 834498 Remove usage of setPageTitle and isVisited from Seamonkey's tests
  • Fixed bug 856208 Stop using global-history;2 in SeaMonkey code
  • Fixed bug 827235 Add plugin-hang-ui@BIN_SUFFIX@ to SeaMonkey package manifest
  • Took care of SeaMonkey Facebook page






  • bug 831993 convert nsISupportsArray m_serversToGetNewMailFor variable from nsPop3IncomingServer.cpp to something better.

Fixed, needs uplift:

  • bug 846763 Browser Feed Preview is broken due to xbl_scopes.

Fixed, possibly should uplift:

Fixed, may need uplift:

  • bug 856406 Tabbed browser should use favicon sevice in a privacy-aware way.

Previously fixed, but may need uplift:

  • bug 844497 Open Location dialog should not save state when opened in a private window.
  • bug 849440 Private downloads don't update.
  • bug 851304 nsContextMenu.js save as handler creates a channel without regard for privacy status.

Working on:

Waiting for review:

  • bug 839891 Implement optional taskbar preview-per-tab.
  • bug 854867 Click-to-play no longer respects per-site permissions.
  • bug 856571 Move accesskey for Error Console's filter box back (Toolkit).
  • bug 855631 Get New Messages for all accounts does not work.



  • bug 852496 [Lightning/SeaMonkey] The image for the delete button in the Event/Task Edit Dialog is messed up.

Working on:

  • bug 849525 Clean up mailnews/subscribe.{js|xul}
  • bug 852499 Port bug 835730 (Properly tear down components when the profile is being shut down) to SeaMonkey.
  • bug 856322 Private Browsing changes for browser feed preview.


  • Did some reviews.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.




  • bug 847182 Extend Glossary with new Privacy & Security terms
  • bug 849359 Print button is misaligned in the Composer and Message Composition toolbars with the Modern theme
  • bug 852809 Explain what happens when Safe Browsing blocks a website
  • bug 855684 Use opacity rather than hard-coded colors for signature display

Working on:

  • bug 856454 Add ability to customise new mail alert information







    • bug 840003 Icons for special IMAP folder (Inbox, trash, ...) are not shown when folder is shared
      • Tested by reporter on 2.19a1 trunk, ported to 2.18a2 aurora, not ported to 2.17 beta due to imminent merge.

(move to "feature list, planning" above?)
In Sm 2.19a1, creating a new permission for a hostname which doesn't have any yet is unobvious and tedious:

  1. Open the Data Manager.
  2. Select * (not the concerned hostname) in the left pane. ←
  3. Select the 'Permissions' tab.
  4. Click [ Add ] at bottom.
  5. Fill in the desired hostname.
  6. Select the desired permission.
  7. Unselect the [x] Default checkbox.
  8. Change the permission value. ←
  9. If desired, set the value back to what it seemed to be before.
  • If you leave the * Permissions tab before step 8, no permission will be set. ←
  • If you leave it at step 8, it may be set incorrectly.
  • Steps marked ← are those I (tonymec) regard as unobvious.
  • Example: Try allowing cookies for host "" if you don't yet have any permissions for that site.

(move to "Extension Compatibility Tracking" above?)
Since almost a year, all SEAMONKEYsomething tags in the ChatZilla repository have been applied to branches where no code changes are made (the only file modified in those branches is .hgtags and sometimes install.rdf). This sounds seriously wrong to me: it would mean that SeaMonkey versions other than Trunk are now being shipped with a built-in ChatZilla whose growth was arrested on 24 April 2012 (the default branch ancestor to branches SEA_12_RELBRANCH and later), and in particular that releases 0.9.89 and 0.9.90 of ChatZilla were judged good enough for AMO but not for SeaMonkey. — Or are those SEAMONKEYsomething tags actually unused, in favour of the CHATZILLAsomething tags which are on the default branch of the repository?
On further thought, these built-in versions of cZ should be updated to the latest version available at AMO the first time SeaMonkey checks for updates.

Any other business?

  • Basic Private Browsing support has been turned on and most things should work but some edge cases have probably been missed. Testing would be appreciated! Please file bugs as blocking the meta bug 460895.
  • The next Bug Day: Tonymec says either some time after Easter holiday, or during the holiday, depending what we decide. Easter holiday in Belgium is 1-14 April this year. Exact date TBD.
    • Need serious discussion about exactly what bug days should change, what they are for, etc.
  • Test failures
    • qawanted, especially on Linux and MacOSX specific issues: reproducing and reporting would already help.
    • Serge says that on Linux and MacOSX, he just needs someone to actually run the tests and report what they see (screen, console, etc). For example, there is a Mac test about Ctrl+W not working. This should be so trivial.
    • Tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.
    • IanN suggests reaching out to the user community using the newsgroups and forums.
    • Ratty to liaise with Serge when he gets back on doing a write up how the community can help us with this.