Confirm
2,242
edits
Changes
copied from 2016-01-05 minutes
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|« last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting »]]</small>
'''SeaMonkey Meeting Details'''
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=19&month=1&year=2016&hour=13&min=0&sec=0&p1=0 19 January, 2016, 13:00 UTC]
** (8am Eastern, 1pm UK, 2pm Central Europe, 9pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** I propose Frank-Rainer Grahl who's been doing a lot of testing and bug reporting on Windows recently, mostly on own-compiled W64 builds; also some bug fixing. Any seconds? — [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 10:32, 26 December 2015 (PST)
** Seconded by Ratty and IanN
=== 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'''
* Need to port Sync 1.5 to SeaMonkey - IanN has spoken briefly to ewong about options, Ratty might be able to help too.
* {{Bug|1198340}} The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
** Unfortunately nobody knows exactly how addons.mozilla.works because there's no full time developer working on AMO. Ratty was given {{Bug|1009759}} as an example. So now we need someone who knows python+django.
** About specific aspects of this problem, see: {{bug|1230796}}, {{bug|1230804}}, {{bug|1230806}} and maybe more.
** [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don't have to worry about the python stuff.
'''CLOSED'''
* —
=== Status of the SeaMonkey Buildbot Master and Tree ===
<!--Please update accordingly-->
* Notes:
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be until january at earliest.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2013 would likely solve this and other bustages.
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
** Buildmaster is up and running, and produces en-US builds, see 9/16 meeting's [[SeaMonkey/StatusMeetings/2014-09-16#Agenda|Friends of the Fish Tank]]. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
** {{Bug|1083689}} Langpacks aren't updated when auto-updating SeaMonkey because they aren't uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
** For various reasons we don't have a working SeaMonkey Treeherder.
** wrt {{bug|1155011}}, we already have a Soccoro token. The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
* [8th December 2015]
* No Update. Ewong is hospitalized. Get well soon!
* Excluding Windows, the tree is green for most part. We're down one osx64 slave.
* Re: Tests. Still broken.
** Currently {{bug|1209378}} is in progress to fix the perma-brokeness of our testing infrastructure; but it is 'hard'.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
<!-- Comment out this section if nothing new fixed -->
<!-- ==== Fixed Stuff Since Last Meeting ====
-->
=== Release Train ===
* SeaMonkey 2.39 was released November 8th, 2015.
* SeaMonkey 2.40 beta has been cancelled.
* SeaMonkey 2.40 final released/scheduled ???
* Last merge was December 14th as scheduled.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
=== Extensions and Plugins Compatibility Tracking ===
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* Lightning button icons are not shown on the mail-toolbox making them invisible. Fixed in {{Bug|1223898}} but we should consider moving the CSS from suite to Lighting.
* We are looking for a new place to host the [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] for the Add-on Converter in order to make it easy to maintain and to serve as the main database for the AMO browsing extension in the future. The details are in [http://forums.mozillazine.org/viewtopic.php?p=14168717#p14168717 this post].
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>This tool goes a little further beyond simply modifying install.rdf - it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there's only so much an automated tool like that can do.
** '''[http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=217009 Lemon Juice]''' continues to improve his already impressive Addon Converter. The source is now available on GitHub [https://github.com/lemon-juice/addonconverter].
** looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [http://forums.mozillazine.org/viewtopic.php?f=40&t=2834855&start=270#p14168717], {{bug|1145026}}.
** Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. -- [[User:Rrbd|Rrbd]] ([[User talk:Rrbd|talk]]) 09:59, 16 August 2015 (PDT)
** Ratty filed {{Bug|1130390}} to add a link on [http://www.seamonkey-project.org/ seamonkey-projects.org] to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
** The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups.
* The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
** {{Bug|516026}} Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
** {{Bug|1130854}} Package Lightning with Thunderbird for c-c and c-a builds.
** {{Bug|1113183}} Integrate Lightning Into Thunderbird by Default.
** {{Bug|1130852}} Add opt-in dialog to promote Calendar integration [Thunderbird].
* Ratty has the '''Firefox Devtools up and running'''. We can now use the Firefox Devtools debugger in both remote and local mode.
** Venkman is now totally retired '''R.I.P.'''.
=== 2.x (Last, Current, Next) ===
* SeaMonkey Statistics can be viewed at [https://dataviz.mozilla.org/t/public/views/SeamonkeyADI/VersionChannelADI?:embed=y#1 https://dataviz.mozilla.org] Across all channels we have an approximate ADU of 120k.
** Ratty suggests embedding these graphs somewhere on [http://www.seamonkey-project.org/ seamonkey-projects.org] or [https://dev.seamonkey.at/ https://dev.seamonkey.at]
** {{Bug|1133728}} Look at embedding dataviz information into the SeaMonkey website.
** '''Links are broken again. Dataviz views now needs a SSO login. We need to find out how to expose a limited view for public consumption {{bug|1173006}}.'''
<!--* 2.16 had ~X ADU by Tuesday 12th March and has had ~Y downloads so far.
** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.-->
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
==== 2.40 ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey240&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey240&type0-0-0=equals&value0-0-0=%3F tracking requests] (3)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.40 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey240&f2=target_milestone&f5=cf_status_seamonkey239&f6=cf_status_seamonkey238&v2=2.40 fixed] (15)
* [http://www.seamonkey-project.org/releases/seamonkey2.40/ SeaMonkey 2.40 Release Notes]
==== 2.Next ====
* '''We have official permission to use the Firefox FxA 2.0 sync servers!''' We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
** {{Bug|1003434}} Add support for about:sync-progress.
* Stalled. Needs a kick.
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
** {{Bug|476108}} GetShortPathNameW fails under some NTFS junctions [patchlove].
<!-- ** — -->
* Current breakages:
** {{Bug|1209875}} did break any builds of 2.41+ containing a localized ChatZilla - {{bug|1213641}} filled
<!--Please update if necessary-->
** No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
* Mozilla-central bugs that affect us:
** Changes to Safe Browsing.
** Firefox is currently changing styles of several Toolkit pages
*** already affected: config.xul for about:config, {{bug|1125636}}
*** Toolkit meta bug for about:* pages: {{bug|1097111}} - SeaMonkey tracking in {{bug|1133743}}
*** Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
*** Fallout thus far: {{bug|1133582}} about:config ''(Modern)''
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
*** mozilla-central {{bug|1189918}} and {{bug|1190465}} allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey {{Bug|1022354}} will move theme overrides to the theme manifests.
**** affected pages that should be reverted are about:config [{{Bug|1222816}}], about:addons [{{Bug|1222817}}], about:support [{{Bug|1222818}}] (look ok in Modern but hurt in the Default theme).
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
*** {{Bug|912031}} Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
** '''The C++ downloads manager backend nsIDownloadManager is being decommissioned'''. Firefox and Thunderbird have migrated to jsdownloads.
** {{Bug|825588}} Asynchronous JavaScript API for downloads and {{Bug|851471}} Decommission nsIDownloadManager. Tracked in:
*** {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''Neil has a WIP patch on hand'''.
** We've picked up he default for <tt>security.tls.version.min</tt> from Mozilla Core, but <tt>security.tls.version.fallback-limit</tt> is new. So we need to consider adding the latter to our preferences UI ({{Bug|1123673}}).
*** Currently unclear whether or not this should be done after {{bug|1084025}} disable insecure TLS version fallback entirely by default [https://bugzilla.mozilla.org/show_bug.cgi?id=1123673#c6]
*** alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 21 new, 6 fixed, 16 triaged.
* good triaging effort, average number of new bugs filed.
* '''Ratty has a SeaMonkey build with a working Firefox Devtools!!!!''' Relevant patches:
** {{Bug|1208112}} Package DevTools client in SeaMonkey now that it's been moved out of /browser/ [checked-in].
** {{Bug|1223338}} Add DevTools client L10N language files to SeaMonkey builds [checked-in].
** {{Bug|1223341}} Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
** {{Bug|1223344}} Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
** Not working yet: WebIDE and Responsive Design. But everything else seems to work.
* Mozilla wants to '''separate Firefox and Thunderbird, in infrastructure and organizationally''', which will likely affect SeaMonkey as well
** discussions in [https://groups.google.com/d/msg/mozilla.governance/kAyVlhfEcXg/Eqyx1X62BQAJ mozilla.governance], [https://groups.google.com/forum/#!topic/mozilla.dev.apps.seamonkey/MvmEOIOXPxE mozilla.dev.apps.seamonkey], [https://groups.google.com/forum/#!topic/tb-planning/bigvCJtidHE tb-planning], [https://blog.lizardwrangler.com/2015/12/03/thunderbird-update/ blog.lizardwrangler.com]
** unclear at this time what "separating the infrastructure" means
** likely goes hand-in-hand with planned reduction of key features and future deprecation of the Gecko rendering engine
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
** {{Bug|1222546}} Product plan: remove support for heavyweight themes
*** if effective for all Toolkit applications, would render most 3rd-party themes disfunct
*** no sufficiently plausible specifics provided 'why' full themes 'must' no longer be supported
**** no clear statements by the Firefox drivers, bug has been restricted for comments since
**** discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
***** see bsmedberg's post [https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/5306/14 #14], targeted for Gecko 49 (April 2016).
*** may prohibit Modern theme being shipped with or installed in SeaMonkey
*** removal is "decided" without any clear alternative envisioned
* '''IanN''' thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. '''Tonymec''' will post a reminder to newsgroups / forums. See {{Bug|1092632}} <tt>(Sm_tri_HowTo) Document how to triage SeaMonkey bugs</tt>.
** The HowTo page has been moved to [[SeaMonkey/QA/Triage HowTo]]. If no one objects, {{bug|1092632}} will be RESOLVED FIXED after the New Year holidays.
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929>=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 64 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 5 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 1 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 15 feedback]
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
*'''TODO:'''
** Encrypted Media Extensions / Digital Rights Management
*** {{Bug|1127784}} added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
*** more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
* '''What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as "official" ?'''
On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official".
So — how are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".
Maybe change the online documentation? (perhaps as part of {{bug|1208822}} "System Requirements page needs update"?)
— [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 13:56, 7 October 2015 (PDT)
* [ewong:] what's the prerequisites of making the Linux64 builds 'official' aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. {{bug|1209378}}
--- Discussion on locale translations for DOMi and Chatzilla ---
* [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See {{Bug|1229810}} Port {{Bug|1228444}} and {{Bug|1228467}} to Chatzilla.
* [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
* [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
* [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
* [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB's new merged (c-c + m-c) repository?
* [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don't know how this will work.
* [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.
=== 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).
==== Aqualon ====
==== Callek ====
==== ewong ====
==== frg ====
==== IanN ====
==== InvisibleSmiley ====
==== KaiRo ====
==== mcsmurf ====
==== Misak ====
==== Mnyromyr ====
==== Neil ====
==== Px ====
==== Rainer Bielefeld ====
==== Ratty ====
==== rsx11m ====
Waiting for checkin on comm-central:
* {{Bug|1229270}} Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.
May need retargeting:
* {{Bug|1123673}} Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.
Other:
* Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
* End-user information and discussion on [http://forums.mozillazine.org/viewforum.php?f=51 MozillaZine].
==== sgautherie ====
==== stefanh ====
==== tonymec ====
=== Any other business? ===
* —
'''SeaMonkey Meeting Details'''
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=19&month=1&year=2016&hour=13&min=0&sec=0&p1=0 19 January, 2016, 13:00 UTC]
** (8am Eastern, 1pm UK, 2pm Central Europe, 9pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** I propose Frank-Rainer Grahl who's been doing a lot of testing and bug reporting on Windows recently, mostly on own-compiled W64 builds; also some bug fixing. Any seconds? — [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 10:32, 26 December 2015 (PST)
** Seconded by Ratty and IanN
=== 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'''
* Need to port Sync 1.5 to SeaMonkey - IanN has spoken briefly to ewong about options, Ratty might be able to help too.
* {{Bug|1198340}} The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
** Unfortunately nobody knows exactly how addons.mozilla.works because there's no full time developer working on AMO. Ratty was given {{Bug|1009759}} as an example. So now we need someone who knows python+django.
** About specific aspects of this problem, see: {{bug|1230796}}, {{bug|1230804}}, {{bug|1230806}} and maybe more.
** [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don't have to worry about the python stuff.
'''CLOSED'''
* —
=== Status of the SeaMonkey Buildbot Master and Tree ===
<!--Please update accordingly-->
* Notes:
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be until january at earliest.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2013 would likely solve this and other bustages.
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
** Buildmaster is up and running, and produces en-US builds, see 9/16 meeting's [[SeaMonkey/StatusMeetings/2014-09-16#Agenda|Friends of the Fish Tank]]. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
** {{Bug|1083689}} Langpacks aren't updated when auto-updating SeaMonkey because they aren't uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
** For various reasons we don't have a working SeaMonkey Treeherder.
** wrt {{bug|1155011}}, we already have a Soccoro token. The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
* [8th December 2015]
* No Update. Ewong is hospitalized. Get well soon!
* Excluding Windows, the tree is green for most part. We're down one osx64 slave.
* Re: Tests. Still broken.
** Currently {{bug|1209378}} is in progress to fix the perma-brokeness of our testing infrastructure; but it is 'hard'.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
<!-- Comment out this section if nothing new fixed -->
<!-- ==== Fixed Stuff Since Last Meeting ====
-->
=== Release Train ===
* SeaMonkey 2.39 was released November 8th, 2015.
* SeaMonkey 2.40 beta has been cancelled.
* SeaMonkey 2.40 final released/scheduled ???
* Last merge was December 14th as scheduled.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
=== Extensions and Plugins Compatibility Tracking ===
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* Lightning button icons are not shown on the mail-toolbox making them invisible. Fixed in {{Bug|1223898}} but we should consider moving the CSS from suite to Lighting.
* We are looking for a new place to host the [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] for the Add-on Converter in order to make it easy to maintain and to serve as the main database for the AMO browsing extension in the future. The details are in [http://forums.mozillazine.org/viewtopic.php?p=14168717#p14168717 this post].
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>This tool goes a little further beyond simply modifying install.rdf - it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there's only so much an automated tool like that can do.
** '''[http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=217009 Lemon Juice]''' continues to improve his already impressive Addon Converter. The source is now available on GitHub [https://github.com/lemon-juice/addonconverter].
** looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [http://forums.mozillazine.org/viewtopic.php?f=40&t=2834855&start=270#p14168717], {{bug|1145026}}.
** Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. -- [[User:Rrbd|Rrbd]] ([[User talk:Rrbd|talk]]) 09:59, 16 August 2015 (PDT)
** Ratty filed {{Bug|1130390}} to add a link on [http://www.seamonkey-project.org/ seamonkey-projects.org] to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
** The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups.
* The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
** {{Bug|516026}} Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
** {{Bug|1130854}} Package Lightning with Thunderbird for c-c and c-a builds.
** {{Bug|1113183}} Integrate Lightning Into Thunderbird by Default.
** {{Bug|1130852}} Add opt-in dialog to promote Calendar integration [Thunderbird].
* Ratty has the '''Firefox Devtools up and running'''. We can now use the Firefox Devtools debugger in both remote and local mode.
** Venkman is now totally retired '''R.I.P.'''.
=== 2.x (Last, Current, Next) ===
* SeaMonkey Statistics can be viewed at [https://dataviz.mozilla.org/t/public/views/SeamonkeyADI/VersionChannelADI?:embed=y#1 https://dataviz.mozilla.org] Across all channels we have an approximate ADU of 120k.
** Ratty suggests embedding these graphs somewhere on [http://www.seamonkey-project.org/ seamonkey-projects.org] or [https://dev.seamonkey.at/ https://dev.seamonkey.at]
** {{Bug|1133728}} Look at embedding dataviz information into the SeaMonkey website.
** '''Links are broken again. Dataviz views now needs a SSO login. We need to find out how to expose a limited view for public consumption {{bug|1173006}}.'''
<!--* 2.16 had ~X ADU by Tuesday 12th March and has had ~Y downloads so far.
** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.-->
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
==== 2.40 ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey240&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey240&type0-0-0=equals&value0-0-0=%3F tracking requests] (3)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.40 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey240&f2=target_milestone&f5=cf_status_seamonkey239&f6=cf_status_seamonkey238&v2=2.40 fixed] (15)
* [http://www.seamonkey-project.org/releases/seamonkey2.40/ SeaMonkey 2.40 Release Notes]
==== 2.Next ====
* '''We have official permission to use the Firefox FxA 2.0 sync servers!''' We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
** {{Bug|1003434}} Add support for about:sync-progress.
* Stalled. Needs a kick.
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
** {{Bug|476108}} GetShortPathNameW fails under some NTFS junctions [patchlove].
<!-- ** — -->
* Current breakages:
** {{Bug|1209875}} did break any builds of 2.41+ containing a localized ChatZilla - {{bug|1213641}} filled
<!--Please update if necessary-->
** No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
* Mozilla-central bugs that affect us:
** Changes to Safe Browsing.
** Firefox is currently changing styles of several Toolkit pages
*** already affected: config.xul for about:config, {{bug|1125636}}
*** Toolkit meta bug for about:* pages: {{bug|1097111}} - SeaMonkey tracking in {{bug|1133743}}
*** Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
*** Fallout thus far: {{bug|1133582}} about:config ''(Modern)''
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
*** mozilla-central {{bug|1189918}} and {{bug|1190465}} allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey {{Bug|1022354}} will move theme overrides to the theme manifests.
**** affected pages that should be reverted are about:config [{{Bug|1222816}}], about:addons [{{Bug|1222817}}], about:support [{{Bug|1222818}}] (look ok in Modern but hurt in the Default theme).
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
*** {{Bug|912031}} Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
** '''The C++ downloads manager backend nsIDownloadManager is being decommissioned'''. Firefox and Thunderbird have migrated to jsdownloads.
** {{Bug|825588}} Asynchronous JavaScript API for downloads and {{Bug|851471}} Decommission nsIDownloadManager. Tracked in:
*** {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''Neil has a WIP patch on hand'''.
** We've picked up he default for <tt>security.tls.version.min</tt> from Mozilla Core, but <tt>security.tls.version.fallback-limit</tt> is new. So we need to consider adding the latter to our preferences UI ({{Bug|1123673}}).
*** Currently unclear whether or not this should be done after {{bug|1084025}} disable insecure TLS version fallback entirely by default [https://bugzilla.mozilla.org/show_bug.cgi?id=1123673#c6]
*** alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 21 new, 6 fixed, 16 triaged.
* good triaging effort, average number of new bugs filed.
* '''Ratty has a SeaMonkey build with a working Firefox Devtools!!!!''' Relevant patches:
** {{Bug|1208112}} Package DevTools client in SeaMonkey now that it's been moved out of /browser/ [checked-in].
** {{Bug|1223338}} Add DevTools client L10N language files to SeaMonkey builds [checked-in].
** {{Bug|1223341}} Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
** {{Bug|1223344}} Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
** Not working yet: WebIDE and Responsive Design. But everything else seems to work.
* Mozilla wants to '''separate Firefox and Thunderbird, in infrastructure and organizationally''', which will likely affect SeaMonkey as well
** discussions in [https://groups.google.com/d/msg/mozilla.governance/kAyVlhfEcXg/Eqyx1X62BQAJ mozilla.governance], [https://groups.google.com/forum/#!topic/mozilla.dev.apps.seamonkey/MvmEOIOXPxE mozilla.dev.apps.seamonkey], [https://groups.google.com/forum/#!topic/tb-planning/bigvCJtidHE tb-planning], [https://blog.lizardwrangler.com/2015/12/03/thunderbird-update/ blog.lizardwrangler.com]
** unclear at this time what "separating the infrastructure" means
** likely goes hand-in-hand with planned reduction of key features and future deprecation of the Gecko rendering engine
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
** {{Bug|1222546}} Product plan: remove support for heavyweight themes
*** if effective for all Toolkit applications, would render most 3rd-party themes disfunct
*** no sufficiently plausible specifics provided 'why' full themes 'must' no longer be supported
**** no clear statements by the Firefox drivers, bug has been restricted for comments since
**** discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
***** see bsmedberg's post [https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/5306/14 #14], targeted for Gecko 49 (April 2016).
*** may prohibit Modern theme being shipped with or installed in SeaMonkey
*** removal is "decided" without any clear alternative envisioned
* '''IanN''' thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. '''Tonymec''' will post a reminder to newsgroups / forums. See {{Bug|1092632}} <tt>(Sm_tri_HowTo) Document how to triage SeaMonkey bugs</tt>.
** The HowTo page has been moved to [[SeaMonkey/QA/Triage HowTo]]. If no one objects, {{bug|1092632}} will be RESOLVED FIXED after the New Year holidays.
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929>=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 64 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 5 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 1 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 15 feedback]
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
*'''TODO:'''
** Encrypted Media Extensions / Digital Rights Management
*** {{Bug|1127784}} added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
*** more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
* '''What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as "official" ?'''
On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official".
So — how are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".
Maybe change the online documentation? (perhaps as part of {{bug|1208822}} "System Requirements page needs update"?)
— [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 13:56, 7 October 2015 (PDT)
* [ewong:] what's the prerequisites of making the Linux64 builds 'official' aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. {{bug|1209378}}
--- Discussion on locale translations for DOMi and Chatzilla ---
* [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See {{Bug|1229810}} Port {{Bug|1228444}} and {{Bug|1228467}} to Chatzilla.
* [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
* [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
* [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
* [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB's new merged (c-c + m-c) repository?
* [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don't know how this will work.
* [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.
=== 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).
==== Aqualon ====
==== Callek ====
==== ewong ====
==== frg ====
==== IanN ====
==== InvisibleSmiley ====
==== KaiRo ====
==== mcsmurf ====
==== Misak ====
==== Mnyromyr ====
==== Neil ====
==== Px ====
==== Rainer Bielefeld ====
==== Ratty ====
==== rsx11m ====
Waiting for checkin on comm-central:
* {{Bug|1229270}} Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.
May need retargeting:
* {{Bug|1123673}} Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.
Other:
* Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
* End-user information and discussion on [http://forums.mozillazine.org/viewforum.php?f=51 MozillaZine].
==== sgautherie ====
==== stefanh ====
==== tonymec ====
=== Any other business? ===
* —
