From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details


  • Who's taking minutes? -> Ratty

Action Items

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



  • Get permission from Google to use their geolocation JSON service [KaiRo]. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step. Sorry that I can not be more specific at this time." - We can only wait right now.


  • File bug on target milestone and flags for 2.1a1 [KaiRo]. Filed and already fixed as bug 512086 together with the 1.1.19 flags/keyword.

SeaMonkey 2.0 Beta 2

open blockers (4) blocker requests (0)

  • IanN has started triaging nominations, KaiRo finished them!
  • Code freeze: September 1 - string freeze August 27 (both 23:59 Pacific).
  • Targeted ship date: September 8 (Firefox 3.0.14/3.5.3 are targeted Sep 9).
    • Thunderbird is targeting Beta4 release on 22nd September with 11th September for code freeze.
    • We need to care that they keep shared code stable during the timeframe we need, and the strings in suite/ need to be frozen during our string freeze, which includes mailnews strings. The code freeze period for us should be fairly short, if we have no blockers left on Sep 1, we can do builds on Sep 2 and unfreeze immediately. The string freeze is the real impact.
  • Tabmail is the big missing feature.
    • Should be in final review stages, biggest part is probably IanN's review.
  • The API changes of bug 474701 would be nice to get, Lightning uses some part of it, filed bug 509324 for that.
  • This is our last beta, and that means that September 1st is also feature freeze for the 2.0 series! Exceptions will only be granted in rare and really-high-value cases.
  • Do we have to look for bugs that may need help making the string freeze?
    • If we have more features to land for the 2.0 cycle, we should really get them pushed into the tree now or wait for 2.1, unless they are really high reward and we think we really want them in 2.0.
    • Thunderbird can't guarantee that they can hold string freeze past the 2nd.
    • suite/ will accept new strings for a while in September, but we want to keep changes small once we're officially feature-frozen next Tuesday.
    • If we have all blockers resolved by code freeze next Tuesday, we can start the release process with tagging on Wednesday and once the relbranch is tagged, we can unfreeze.
  • Current blockers: status?
    • bug 474709 Depends on the review, but mcsmurf thinks the patch is good. Note: has string impact.
    • bug 507896 Should not be that difficult to fix [mcsmurf].
    • bug 505832 The relevant AMO people have been poked [KaiRo].

SeaMonkey 2.0 Final

open blockers (4) blocker requests (36) open wanted (18) wanted requests (31)

  • IanN will start triaging blocker and wanted requests.
    • We can probably put off a number of things, where they sound useful, to 2.1a1 or 2.1.
  • Target schedule: Freeze October 6, ship mid-October?
    • Thunderbird is expecting RC1 freeze on 3rd November but string freeze also on October 6 or so.
    • Freeze on October 6th should allow at least a week of string freeze for final and allow us for some time of candidate testing, whether we push them as public RC releases or not.
    • We can look at more details closer to when 2.0b2 is about to go public.

Feature List, Planning

Bug statistics for last two (full) weeks: 62 new, 26 fixed, 24 triaged.

Major wanted/needed features:


  • Toolbar customization aftermath [Ratty]
    • bug 481862 We still need small button icons for modern in MailNews. Needs someone who understands both css and svg/graphics.
    • bug 509209 Implement Customizable Toolbars in SeaMonkey Message Compose. Has patch. Waiting reviews.
  • bug 460960 Port Thunderbird tabbed interface to MailNews.
    • It is to be hoped that we can get positive reviews from both IanN and Neil before Thursday so that we can finally land it.
  • bug 460699 Make the default theme look better on mac.
    • landed!
  • bug 456757 Modern theme update [Ratty].
    • bug 493022 Add mozapps/ to the modern theme. landed!.
    • Now working on bug 465924 Modern Update: changes in global/. textbox.css, and wizard.css need some minor polish. notification.css needs to be updated but depends on bug 512254 Port bug 429282 (Land new windows icons (20080416)).
  • bug 348720 New icon set for "SeaMonkey Default Theme".
    • No News.
  • bug 460953 Port jminta's kill-rdf to SeaMonkey where applicable.
    • sgautherie is working his way steadily through porting all the relevant Thunderbird bugs.

We also should take a careful look at the other items on wanted-seamonkey2+ for things like things like:

  • bug 436794 Enable Mac OS X system address book per default and add UI.
  • bug 508039 Port |Bug 456439 - add about:rights and a "Know Your Rights" infobar to Firefox| to SeaMonkey.

If there's anything on that list you think we shouldn't take for 2.0 any more, please notify KaiRo, so we can push them to 2.1.


  • bug 410613 OpenSearch. helpwanted.
    • We need to check if OpenSearch can support all our existing functionality, for example the INTEPRETS section in Sherlock search plugins. Mnyromyr will check on that, and on how extensible the Firefox code is.


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







  • Usual testing, reviewing and commenting.


  • Started release process for SeaMonkey 1.1.18, which has a major NSS upgrade. We found one regression in Windows candidates, a packaging miss rendering SSL unusable, patch is about to be checked in and builds regenerated.
  • As always, my blog has more detailed status about my work.


  • Checked in bug 483980 Allow history/bookmark observer components to register with a startup category which fixes bug 484175 History Import from SeaMonkey 1.1.x is not working
  • Fixed bug 495680 Problems with import of downloads.rdf after switch to toolkit download manager
  • Got bug 481836 URLbar autocomplete fills in nonexistant URL going again
  • Created patch for bug 474709 Subscribing to a feed (triggered by an external application) while no RSS account is present, does nothing


  • Started to port sessionstore bugs again, there is a lot them yet unported. Now working on:
    • bug 511635 Port Bug 455070 [Make sessionStorage object conform the WHATWG spec] to SeaMonkey.
    • bug 510890 Port Bug 394759 (Add undo close window feature) to SeaMonkey.
    • bug 511640 Port Bug 490040 [Reattaching a lone tab into another window causes an empty window to be added to Recently Closed Windows].
    • bug 511823 Port Bug 494543 [Can't add items to shopping cart] to SeaMonkey.




  • Bugs Fixed:
    • bug 509367 Race condition during parallel build.
    • bug 510786 addrbook.gif needs some transparency.
    • bug 511797 [SeaMonkey] mozilla-central builds do not compile after bug 380917 landing.


  • Bugs Fixed:
    • bug 507871 "New Msg" button: Highlight default action in the pull down menu.
    • bug 493022 Add mozapps/ to the modern theme.
  • Working on:
    • bug 465924 Modern Update: changes in global/.
    • bug 509209 Implement Customizable Toolbars in SeaMonkey Message Compose.
    • bug 511096 Port FUEL Bug 458688 (test browser_Browser.js still times out occasionally).
  • Bug triage and bug discussions.
  • AgitProp and PR in


  • bug 460953 Port jminta's kill-rdf to SeaMonkey where applicable
    • Landed the 6 simple patches :-)
    • 1 last patch waits for 2(++) major ports:
      • bug 444913 Port |Bug 413781 – XBLify folder-selection menus| to SeaMonkey
        • mcsmurf replied he believes we don't have enough review resources for this currently.
      • bug 507601 Port |Bug 414038 - Replace rdf-driven folder pane with a js-driven/non-rdf treeview| to SeaMonkey
        • Landed the 2 simple patches :-)
        • Filed bug 510793 Actually change folder pane from rdf to js, in SeaMonkey
          • Current time target would be between b2 and final...
        • Filed bug 510685 SeaMonkey does want a fix for |Bug 464973 - "Expanded Columns" in the folder pane are no longer available|, unlike Thunderbird
        • Filed bug 510646 Tracking future bugs for "Port |Bug 414038 - Replace rdf-driven folder pane with a js-driven/non-rdf treeview| to SeaMonkey"
      • bug 507676 Port |Bug 435804 - Remaining rdf cleanup for FilterListDialog| to SeaMonkey
        • Depends on bug 444913
  • bug 509324 Port the thread pane / folder display refactoring from bug 474701 to SeaMonkey
    • "Triaged" patches and blocking bugs of bug 474701.
    • KaiRo confirmed only one (big) patch needs to be ported for this bug.
  • Fixed SeaMonkey bugs:
    • bug 506850 [MacOSX] mochitest-chrome: test_action_keys_respect_focus.xul reports "Test timed out"
    • bug 509594 [SeaMonkey] mochitest-plain: test_datepicker.xul fails now, conflicts with SeaMonkey (extension) 'QA' menu
    • bug 509847 SearchDialog.js: "Warning: assignment to undeclared variable searchFolderURIs"
    • bug 510716 Port |Bug 421781 - Remove fake-account hooks from front-end| to SeaMonkey
  • And working on other areas... like
    • infrastructure to run tests
    • filing bugs for leaks in (TUnit) tests
    • doing a Windows comm-central-trunk SeaMonkey unit test build, reporting to bug 470184 issue tracking; looking forward to an official build when enough new buildbot slaves can be enabled (bug 464325 follow-ups).




Any other business?

  • Do we have enough machines for when we branch?
    • We are already running a configuration that is build-wise the same as having an actual branched setup, and in terms of having builds for trunk and branch, we have things up and running.
    • In terms of running tests on both, we are at least missing two machines which were promised to us, KaiRo is working with IT and community giving to get that resolved.
    • But even with those machines, we'll be overloaded unless the machines magically get significantly faster. We'll need to take a deeper look into what to do about that later.