Confirm
2,242
edits
Changes
copied from 2017-04-02 minutes
<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -3 week}}|« last meeting]] | [[SeaMonkey/StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting »]]</small>
'''SeaMonkey Meeting Details'''
* Time: Sunday [http://www.timeanddate.com/worldclock/fixedtime.html?day=23&month=4&year=2017&hour=14&min=0&sec=0&p1=0 23 April, 2017, 14:00 UTC]
** (10am Eastern, 3pm UK, 4pm Central Europe, 10pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** '''TBD'''
=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
We should assign people to the open items.
'''NEW'''
* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future. '''frg''' will prepare an "asking for help" draft for the council. When final it will be posted in the various SeaMonkey newsgroups.
* —
'''OPEN'''
* Mozilla plans to check in l20n. Unclear what this means for comm-central and the current l10n build configs. Needs to be monitored.
** {{bug|1107635}} - Rewrite build system l10n repack rules from Makefile rules into a Python script might also affect a timely l10n repack
* Google announced V4 of the safebrowsing api. Firefox adds support for it in {{bug|1167038}}.
** In 2.51+ additional preferences are needed. The blocklist interface will also be changed. You now see errors in a new 2.51 profile. No bug has been filed for this as of now.
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m will open a bug to use the Google key for now in all trees ({{bug|1352850}} created after meeting).
* '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed.
** TODO: Add Adrian Kalla to RelEng team. Overall no change as of today
* '''IanN''' [http://www.seamonkey-project.org/dev/project-areas SeaMonkey project areas] is very outdated. '''IanN''' plans to update the project areas soon.
* Discussions and planning about the future of SeaMonkey and if we should set up own builders are still going on.
** frg asked Adrian about his build config. He runs a small setup: 2 PCs, a Mac and a Jumhost (DD-WRT router). 1 PC is the Buildmaster and second the server with VMs for Windows and Linux building.
** Ratty would like to have a try server.
** frg misses an OSX try server most.
** There would be problems uploading binaries to Mozilla servers. Linux distributors can upload crash-symbols. This would probably be possible.
** An infra architect is now working for Thunderbird. The SeaMonkey project has gotten an invitation to join but nothing has been discussed yet. '''IanN''' asked '''ewong''' if he could get in touch with rkent. A new TB council has been elected and talks could start.
** A joint discussion should take place. Not finalized who organizes this and when.
** Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare.
** Due to cost and availability the generation of daily builds would need to be cut back. The team doesn't see much problems here and a new schedule could be worked out.
** '''IanN''' mentioned taskcluster as an alternative to buildbot. According to '''ewong''' and '''frg''' it looks complex and Mozilla specific.
*** The Thunderbird project plans to hire a designer for a new build infrastructure in the near future.
** There are plans by Mozilla to do cross compiles on Linux for Windows and macOS. Not finalized yet.
* —
'''CLOSED'''
* —
=== Status of the SeaMonkey Buildbot Master and Tree ===
<!--Please update accordingly-->
* Various Bugs open for building.
** OSX64: busted due to {{bug|1260362}}. Yasm 1.2 needs to be installed. (Ratty: Depends on {{Bug|1257904}}. How to get traction on this?)
*** Perma-busted-red: {{bug|958812}}
** Linux64 Nightly: {{bug|1275215}} is still open but Linux is building most of the time.
** Linux64 build: {{bug|1275218}} is still open but Linux is building most of the time.
** Windows building is done on the loaner.
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule.
*** CZ langpacks seem to be disabled by default, so that needs to be sorted.
*** DOMi still needs to be sorted.
*** Lightning l10n upload still needs to be sorted.
* [2nd Apri 2017]
** Tests have been re-enabled to enable us to find out what's busting them. {{bug|1295826}} tracks the fixes for the Testing Infrastructure.
*** All tests are red.
** [comm-central]:
*** All platforms: green
*** See {{bug|1345770}} for current breakages.
*** {{bug|1344411}} - 'Lightweight themes are not supported anymore in SeaMonkey' needs a helping hand. If we just port the Firefox build the titlebar will be overwritten by some themes.
** [comm-aurora]:
*** Linux*: Green
*** OSX64: Orange/Green
*** See {{bug|1334779}} for current breakages.
** [comm-beta]
*** Pretty much Green/Orange.
*** See {{bug|1319091}} for current breakages.
** [comm-release]:
*** Pretty much Green/Orange.
*** See {{bug|1313304}} for current breakages.
** [comm-esr52]:
*** No automation. [Filed {{bug|1352820}}]
*** Broken by uplift of {{bug|1299500}} which also affects Thunderbird and Firefox.
* Notes:
** '''Ewong''' did set up a cron job to do semi regular builds on the loaner machine. The MAC builders can be updated to OSX 10.9. He needs to consult with '''Callek''' first about this.
** Windows nightly trunk builds are only done on the loaner. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008 R2] will likely never happen.
*** '''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 any time soon.
** 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).
** 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.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
<!-- Comment out this section if nothing new fixed -->
==== Fixed Stuff Since Last Meeting ====
* —
<!-- already fixed in the fortnight ending at last meeting
-->
=== Release Train ===
* SeaMonkey 2.46 was released December 22, 2016, tracked in {{Bug|1294433}}
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1336310}} (general beta issues in {{bug|1328886}})
** SeaMonkey 2.48 beta 1 is in candidates [https://archive.mozilla.org/pub/seamonkey/candidates/2.48b1-candidates/build7/]. '''ewong''' wants to figure out if updates from 2.39b1 can be made to work so that the 2.48 release will upgrade from 2.46 without problems.
** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
*** l10n problem is tracked in ({{bug|1231349}}).
*** Chatzilla and DOMi repack problems are also tracked in {{Bug|1315552}}.
*** IanN has locale merge working for Chatzilla and is working on the DOMi repack issues.
*** See also {{Bug|652063}} (Enable localized ChatZilla builds).
** Release notes in {{Bug|1336315}}.
** gtk3 will be disabled for beta and likely release builds. Building with gtk2 currently helds up the build because there are several minor problems in mozilla code. Fixes are redy and will be pushed to the beta branch. '''ewong''' is currently asking for approval because he isn't sure if we could do this. IanN and frg think we did it before and no approval is needed because its branch only.
*** There are at least three problems with gtk3 builds which may not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}, {{Bug|1331208}}).
*** A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version ({{bug|1312215}}).
*** Building releases with gtk2 is only a short time solution and will no longer be possible with Gecko 53 (SM 2.50, thus would still allow 2.49 gtk2 builds). Probably a meta bug for gtk3 compatibility should be created.
** SeaMonkey 2.49 will be build with ALSA support. This has been disabled in Firefox 52 and causes problems for Linux users (see discussion in {{bug|1345661}}).
** Because of the following bugs updates need to be tested if they are still working:
*** {{Bug|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
*** {{Bug|1271761}} Add CPU features/detection to update URL
** 2.48 is 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
** frg mentioned that the 2.48 is getting late and if we should jump directly to 2.49 after the 2.48 beta which is mostly done now for getting the migration to balrog tested. ewong wants a stable 2.48 release as an interim to further test the migration work.
* Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
* ewong: Suggests the following:
** Officially release a linux64 build (incl. tests)
*** Start with comm-central trunk.
*** Not entirely sure what is needed to make it official. Need to correspond with Callek.
** Build an unofficial (contributed build) Win64 build. [akin to the status that Linux64 has now.]
*** Start later with comm-central we need to iron out the build issues, though right now, having just finished a W64 build; but I don't know how the tests are going to work though this will need to wait).
*** Currently tracked by {{bug|482143}}.
* Current plan is to do releases off comm-esr52. No current backup plan other than continue building off comm-release.
** Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
=== Extensions and Plugins Compatibility Tracking ===
* SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. This would fix long standing issues we have with AMO.
** '''Ratty''' and '''IanN''' will meet with the AMO people to discuss this.
** '''Ratty''' and '''IanN''' will meet with the Thunderbird people to discuss this.
** [Ratty] Suggests that if we do this, we can also host the ''Firefox & Thunderbird Add-on Converter for SeaMonkey''.
* '''Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57''' [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** ''new'' add-ons other than WebExtensions will [[Add-ons/2017#Firefox_53|no longer be accepted for signing]] as early as Gecko 53.
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* '''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.
** We are 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}}.
** 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, is mature. 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 [https://addons.mozilla.org/addon/html-validator/ HTML Validator] adds HTML validation to SeaMonkey. [https://addons.mozilla.org/en-US/firefox/addon/html-validator/versions/0.9.7.5.beta The Beta version] is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as [https://validator.w3.org the W3C validator] but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See [http://users.skynet.be/mgueury/mozilla/index.html the developer's site] for details.
* In Gecko 52 obsolete toolkit parts were removed in {{bug|1312143}}. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and were fixed.
=== 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.46 current release ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.46 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_seamonkey246&f2=target_milestone&f5=cf_status_seamonkey245&v2=2.46 fixed] (27)
===== 2.47 skipped =====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey247&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.47 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_seamonkey247&f2=target_milestone&f5=cf_status_seamonkey246&v2=2.47 fixed] (15)
==== 2.48 planned next release ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%3F tracking requests] (3)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 targeted] (1)
[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_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (22)
==== 2.Next ====
* We need someone to work on porting sync 1.5 over to replace legacy sync code. '''Frg was distracted by other bugs and tasks and didn't look into it yet'''.<br />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.
** As an alternative to porting sync setting up a sync 1.1 server might work.
** Sync 1.1 has been removed from the mozilla source tree. If we want sysnc 1.1 to work we need to fork it.
*** Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system.
*** Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox).
* 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:
** —
<!-- ** — -->
<!--Please update if necessary-->
* Mozilla-central bugs that affect us:
** {{Bug|1298243}} 'drag/drop: DataTransfer.types is wrong type'. Building SeaMonkey still works but changes probably need to be ported.
** {{Bug|1276739}} 'replace list.txt with a region-aware JSON file format to allow different search configs...'. Regressions for SeaMonkey are tracked in {{Bug|1300198}}.
*** {{Bug|1300198}} Move list.txt over to JSON once {{bug|1276739}} is in.
**** This will likely break search engines and needs to be looked at.
** 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 has been checked in and broke SeaMonkey 2.51. Tracked in:
*** {{Bug|912031}} Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite. Currently being worked on by IanN and frg for the Data Manager part.
** '''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. '''frg is currently looking into the patch from Neil'''.
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion.
* [rsx11m] did open bug {{bug|1305902}} for certificate pinning. Discussion if it should be enabled for SeaMonkey is still underway. '''Callek''' commented in the bug.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 14 new, 3 fixed, 4 triaged.
* low triaging effort, low number of new bugs filed.
[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 38 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 13 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
* Mozilla wants to '''Move Thunderbird off MoCo infrastructure and onto their own''', which will likely affect SeaMonkey as well
** '''[Ratty:]''' Rkent - Thunderbird leader - would like SeaMonkey to join Thunderbird in this move. This might fix our problem with lack of builders and our PERMA-CLOSED trees due to this lack.
** 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]
** Blog post [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road]
** Separating the infrastructure: [https://groups.google.com/forum/#!topic/tb-planning/i-PSgm_VrOk Build and release: Mozilla's offer].
** '''More recent posts/discussions:'''
*** [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road - Mark Surman]
*** [https://groups.google.com/forum/#!msg/tb-planning/i-PSgm_VrOk/nXAkJgvIHwAJ Build and release: Mozilla's offer (on tb-planning)]
** SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. Check to see what Thunderbirds plan is. We might be able to share costs by sharing on add-ons site for both or even all three comm-central applications ([http://instantbird.com/ Instantbird]).
* '''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 defunct.
*** Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
*** No news about it till now but will likely come with Firefox 57. Unclear if at first it can be pref controlled.
* Rainer started a [https://unofficialseamonkeynews.wordpress.com/2016/06/01/seamonkey-bugfix-coffee-mug-competition/ Coffee-Mug-Competition]. Please let any developers you know to it and post a big '''Help wanted!''' sign.
* SeaMonkey Composer is outdated. Ratty thinks that using backports or parts of KompoZer [http://kompozer.net/] might solve some of the problems.
* x64 Linux and for the first time x64 Windows builds will be made official as soon as possible.
** Unofficial Linux builds just need to be declared official.
** Providing Windows x64 builds is tracked in {{Bug|482143}}.
* The website and wiki are outdated. '''InvisibleSmiley''' no longer maintains the website. For 2.46 the website was updated but it still needs work.
** {{Bug|1253932}} tracked the relnotes for 2.40 and could be used as a start point.
** ''' mcsmurf''' knows how to change the site.
* '''frg''' suggested asking for donations in a future release. Probably during startup or more prominently on the website.
* '''frg''' suggested a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
** '''IanN''' suggests doing small patches which are easier to review.
=== Roundtable - Personal Status Updates ===
'''IanN will handle review requests. Ratty is currently absent.'''
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 ====
==== Rainer Bielefeld ====
==== Ratty ====
==== rsx11m ====
Still planning to look into:
* {{Bug|493217}} add UI pref for media.autoplay.enabled
** Move related items to a new Appearance → Media prefpane
* {{Bug|1318852}} Make labels of cmd_properties action-oriented and context-sensitive, e.g. "Edit Contact", "Edit List", etc.
** "real" fix
Awaiting new patch for ui-review:
* {{Bug|1298487}} Modern theme for about:networking
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].
==== stefanh ====
==== tonymec ====
<!-- to be uncommented in next meeting's roundtable
N.B. On April 23 I won't be able to attend -->
* {{Bug|1344411|Bug 1344411 - Lightweight themes are not supported anymore in SeaMonkey}} : RESOLVED FIXED, r=IanN, a(2.51)=IanN, 2.50-unaffected, 2.51-fixed, 2.52-fixed, verifyme
** Patch written with much needed help by frg at start and finish, tested on Windows by frg and on L64 by me by hacking the omni.ja, awaits verification on both 2.51 and 2.52 (which are expected to have moved to Beta and Aurora respectively by the time the meeting is held) on any platform by anyone willing. (Verification on non-Linux may require an owncompiled build.)
=== Any other business? ===
* —
'''SeaMonkey Meeting Details'''
* Time: Sunday [http://www.timeanddate.com/worldclock/fixedtime.html?day=23&month=4&year=2017&hour=14&min=0&sec=0&p1=0 23 April, 2017, 14:00 UTC]
** (10am Eastern, 3pm UK, 4pm Central Europe, 10pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** '''TBD'''
=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
We should assign people to the open items.
'''NEW'''
* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future. '''frg''' will prepare an "asking for help" draft for the council. When final it will be posted in the various SeaMonkey newsgroups.
* —
'''OPEN'''
* Mozilla plans to check in l20n. Unclear what this means for comm-central and the current l10n build configs. Needs to be monitored.
** {{bug|1107635}} - Rewrite build system l10n repack rules from Makefile rules into a Python script might also affect a timely l10n repack
* Google announced V4 of the safebrowsing api. Firefox adds support for it in {{bug|1167038}}.
** In 2.51+ additional preferences are needed. The blocklist interface will also be changed. You now see errors in a new 2.51 profile. No bug has been filed for this as of now.
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m will open a bug to use the Google key for now in all trees ({{bug|1352850}} created after meeting).
* '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed.
** TODO: Add Adrian Kalla to RelEng team. Overall no change as of today
* '''IanN''' [http://www.seamonkey-project.org/dev/project-areas SeaMonkey project areas] is very outdated. '''IanN''' plans to update the project areas soon.
* Discussions and planning about the future of SeaMonkey and if we should set up own builders are still going on.
** frg asked Adrian about his build config. He runs a small setup: 2 PCs, a Mac and a Jumhost (DD-WRT router). 1 PC is the Buildmaster and second the server with VMs for Windows and Linux building.
** Ratty would like to have a try server.
** frg misses an OSX try server most.
** There would be problems uploading binaries to Mozilla servers. Linux distributors can upload crash-symbols. This would probably be possible.
** An infra architect is now working for Thunderbird. The SeaMonkey project has gotten an invitation to join but nothing has been discussed yet. '''IanN''' asked '''ewong''' if he could get in touch with rkent. A new TB council has been elected and talks could start.
** A joint discussion should take place. Not finalized who organizes this and when.
** Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare.
** Due to cost and availability the generation of daily builds would need to be cut back. The team doesn't see much problems here and a new schedule could be worked out.
** '''IanN''' mentioned taskcluster as an alternative to buildbot. According to '''ewong''' and '''frg''' it looks complex and Mozilla specific.
*** The Thunderbird project plans to hire a designer for a new build infrastructure in the near future.
** There are plans by Mozilla to do cross compiles on Linux for Windows and macOS. Not finalized yet.
* —
'''CLOSED'''
* —
=== Status of the SeaMonkey Buildbot Master and Tree ===
<!--Please update accordingly-->
* Various Bugs open for building.
** OSX64: busted due to {{bug|1260362}}. Yasm 1.2 needs to be installed. (Ratty: Depends on {{Bug|1257904}}. How to get traction on this?)
*** Perma-busted-red: {{bug|958812}}
** Linux64 Nightly: {{bug|1275215}} is still open but Linux is building most of the time.
** Linux64 build: {{bug|1275218}} is still open but Linux is building most of the time.
** Windows building is done on the loaner.
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule.
*** CZ langpacks seem to be disabled by default, so that needs to be sorted.
*** DOMi still needs to be sorted.
*** Lightning l10n upload still needs to be sorted.
* [2nd Apri 2017]
** Tests have been re-enabled to enable us to find out what's busting them. {{bug|1295826}} tracks the fixes for the Testing Infrastructure.
*** All tests are red.
** [comm-central]:
*** All platforms: green
*** See {{bug|1345770}} for current breakages.
*** {{bug|1344411}} - 'Lightweight themes are not supported anymore in SeaMonkey' needs a helping hand. If we just port the Firefox build the titlebar will be overwritten by some themes.
** [comm-aurora]:
*** Linux*: Green
*** OSX64: Orange/Green
*** See {{bug|1334779}} for current breakages.
** [comm-beta]
*** Pretty much Green/Orange.
*** See {{bug|1319091}} for current breakages.
** [comm-release]:
*** Pretty much Green/Orange.
*** See {{bug|1313304}} for current breakages.
** [comm-esr52]:
*** No automation. [Filed {{bug|1352820}}]
*** Broken by uplift of {{bug|1299500}} which also affects Thunderbird and Firefox.
* Notes:
** '''Ewong''' did set up a cron job to do semi regular builds on the loaner machine. The MAC builders can be updated to OSX 10.9. He needs to consult with '''Callek''' first about this.
** Windows nightly trunk builds are only done on the loaner. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008 R2] will likely never happen.
*** '''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 any time soon.
** 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).
** 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.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
<!-- Comment out this section if nothing new fixed -->
==== Fixed Stuff Since Last Meeting ====
* —
<!-- already fixed in the fortnight ending at last meeting
-->
=== Release Train ===
* SeaMonkey 2.46 was released December 22, 2016, tracked in {{Bug|1294433}}
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1336310}} (general beta issues in {{bug|1328886}})
** SeaMonkey 2.48 beta 1 is in candidates [https://archive.mozilla.org/pub/seamonkey/candidates/2.48b1-candidates/build7/]. '''ewong''' wants to figure out if updates from 2.39b1 can be made to work so that the 2.48 release will upgrade from 2.46 without problems.
** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
*** l10n problem is tracked in ({{bug|1231349}}).
*** Chatzilla and DOMi repack problems are also tracked in {{Bug|1315552}}.
*** IanN has locale merge working for Chatzilla and is working on the DOMi repack issues.
*** See also {{Bug|652063}} (Enable localized ChatZilla builds).
** Release notes in {{Bug|1336315}}.
** gtk3 will be disabled for beta and likely release builds. Building with gtk2 currently helds up the build because there are several minor problems in mozilla code. Fixes are redy and will be pushed to the beta branch. '''ewong''' is currently asking for approval because he isn't sure if we could do this. IanN and frg think we did it before and no approval is needed because its branch only.
*** There are at least three problems with gtk3 builds which may not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}, {{Bug|1331208}}).
*** A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version ({{bug|1312215}}).
*** Building releases with gtk2 is only a short time solution and will no longer be possible with Gecko 53 (SM 2.50, thus would still allow 2.49 gtk2 builds). Probably a meta bug for gtk3 compatibility should be created.
** SeaMonkey 2.49 will be build with ALSA support. This has been disabled in Firefox 52 and causes problems for Linux users (see discussion in {{bug|1345661}}).
** Because of the following bugs updates need to be tested if they are still working:
*** {{Bug|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
*** {{Bug|1271761}} Add CPU features/detection to update URL
** 2.48 is 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
** frg mentioned that the 2.48 is getting late and if we should jump directly to 2.49 after the 2.48 beta which is mostly done now for getting the migration to balrog tested. ewong wants a stable 2.48 release as an interim to further test the migration work.
* Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
* ewong: Suggests the following:
** Officially release a linux64 build (incl. tests)
*** Start with comm-central trunk.
*** Not entirely sure what is needed to make it official. Need to correspond with Callek.
** Build an unofficial (contributed build) Win64 build. [akin to the status that Linux64 has now.]
*** Start later with comm-central we need to iron out the build issues, though right now, having just finished a W64 build; but I don't know how the tests are going to work though this will need to wait).
*** Currently tracked by {{bug|482143}}.
* Current plan is to do releases off comm-esr52. No current backup plan other than continue building off comm-release.
** Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
=== Extensions and Plugins Compatibility Tracking ===
* SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. This would fix long standing issues we have with AMO.
** '''Ratty''' and '''IanN''' will meet with the AMO people to discuss this.
** '''Ratty''' and '''IanN''' will meet with the Thunderbird people to discuss this.
** [Ratty] Suggests that if we do this, we can also host the ''Firefox & Thunderbird Add-on Converter for SeaMonkey''.
* '''Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57''' [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** ''new'' add-ons other than WebExtensions will [[Add-ons/2017#Firefox_53|no longer be accepted for signing]] as early as Gecko 53.
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* '''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.
** We are 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}}.
** 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, is mature. 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 [https://addons.mozilla.org/addon/html-validator/ HTML Validator] adds HTML validation to SeaMonkey. [https://addons.mozilla.org/en-US/firefox/addon/html-validator/versions/0.9.7.5.beta The Beta version] is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as [https://validator.w3.org the W3C validator] but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See [http://users.skynet.be/mgueury/mozilla/index.html the developer's site] for details.
* In Gecko 52 obsolete toolkit parts were removed in {{bug|1312143}}. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and were fixed.
=== 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.46 current release ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.46 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_seamonkey246&f2=target_milestone&f5=cf_status_seamonkey245&v2=2.46 fixed] (27)
===== 2.47 skipped =====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey247&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.47 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_seamonkey247&f2=target_milestone&f5=cf_status_seamonkey246&v2=2.47 fixed] (15)
==== 2.48 planned next release ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%3F tracking requests] (3)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 targeted] (1)
[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_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (22)
==== 2.Next ====
* We need someone to work on porting sync 1.5 over to replace legacy sync code. '''Frg was distracted by other bugs and tasks and didn't look into it yet'''.<br />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.
** As an alternative to porting sync setting up a sync 1.1 server might work.
** Sync 1.1 has been removed from the mozilla source tree. If we want sysnc 1.1 to work we need to fork it.
*** Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system.
*** Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox).
* 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:
** —
<!-- ** — -->
<!--Please update if necessary-->
* Mozilla-central bugs that affect us:
** {{Bug|1298243}} 'drag/drop: DataTransfer.types is wrong type'. Building SeaMonkey still works but changes probably need to be ported.
** {{Bug|1276739}} 'replace list.txt with a region-aware JSON file format to allow different search configs...'. Regressions for SeaMonkey are tracked in {{Bug|1300198}}.
*** {{Bug|1300198}} Move list.txt over to JSON once {{bug|1276739}} is in.
**** This will likely break search engines and needs to be looked at.
** 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 has been checked in and broke SeaMonkey 2.51. Tracked in:
*** {{Bug|912031}} Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite. Currently being worked on by IanN and frg for the Data Manager part.
** '''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. '''frg is currently looking into the patch from Neil'''.
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion.
* [rsx11m] did open bug {{bug|1305902}} for certificate pinning. Discussion if it should be enabled for SeaMonkey is still underway. '''Callek''' commented in the bug.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 14 new, 3 fixed, 4 triaged.
* low triaging effort, low number of new bugs filed.
[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 38 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 13 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
* Mozilla wants to '''Move Thunderbird off MoCo infrastructure and onto their own''', which will likely affect SeaMonkey as well
** '''[Ratty:]''' Rkent - Thunderbird leader - would like SeaMonkey to join Thunderbird in this move. This might fix our problem with lack of builders and our PERMA-CLOSED trees due to this lack.
** 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]
** Blog post [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road]
** Separating the infrastructure: [https://groups.google.com/forum/#!topic/tb-planning/i-PSgm_VrOk Build and release: Mozilla's offer].
** '''More recent posts/discussions:'''
*** [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road - Mark Surman]
*** [https://groups.google.com/forum/#!msg/tb-planning/i-PSgm_VrOk/nXAkJgvIHwAJ Build and release: Mozilla's offer (on tb-planning)]
** SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. Check to see what Thunderbirds plan is. We might be able to share costs by sharing on add-ons site for both or even all three comm-central applications ([http://instantbird.com/ Instantbird]).
* '''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 defunct.
*** Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
*** No news about it till now but will likely come with Firefox 57. Unclear if at first it can be pref controlled.
* Rainer started a [https://unofficialseamonkeynews.wordpress.com/2016/06/01/seamonkey-bugfix-coffee-mug-competition/ Coffee-Mug-Competition]. Please let any developers you know to it and post a big '''Help wanted!''' sign.
* SeaMonkey Composer is outdated. Ratty thinks that using backports or parts of KompoZer [http://kompozer.net/] might solve some of the problems.
* x64 Linux and for the first time x64 Windows builds will be made official as soon as possible.
** Unofficial Linux builds just need to be declared official.
** Providing Windows x64 builds is tracked in {{Bug|482143}}.
* The website and wiki are outdated. '''InvisibleSmiley''' no longer maintains the website. For 2.46 the website was updated but it still needs work.
** {{Bug|1253932}} tracked the relnotes for 2.40 and could be used as a start point.
** ''' mcsmurf''' knows how to change the site.
* '''frg''' suggested asking for donations in a future release. Probably during startup or more prominently on the website.
* '''frg''' suggested a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
** '''IanN''' suggests doing small patches which are easier to review.
=== Roundtable - Personal Status Updates ===
'''IanN will handle review requests. Ratty is currently absent.'''
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 ====
==== Rainer Bielefeld ====
==== Ratty ====
==== rsx11m ====
Still planning to look into:
* {{Bug|493217}} add UI pref for media.autoplay.enabled
** Move related items to a new Appearance → Media prefpane
* {{Bug|1318852}} Make labels of cmd_properties action-oriented and context-sensitive, e.g. "Edit Contact", "Edit List", etc.
** "real" fix
Awaiting new patch for ui-review:
* {{Bug|1298487}} Modern theme for about:networking
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].
==== stefanh ====
==== tonymec ====
<!-- to be uncommented in next meeting's roundtable
N.B. On April 23 I won't be able to attend -->
* {{Bug|1344411|Bug 1344411 - Lightweight themes are not supported anymore in SeaMonkey}} : RESOLVED FIXED, r=IanN, a(2.51)=IanN, 2.50-unaffected, 2.51-fixed, 2.52-fixed, verifyme
** Patch written with much needed help by frg at start and finish, tested on Windows by frg and on L64 by me by hacking the omni.ja, awaits verification on both 2.51 and 2.52 (which are expected to have moved to Beta and Aurora respectively by the time the meeting is held) on any platform by anyone willing. (Verification on non-Linux may require an owncompiled build.)
=== Any other business? ===
* —
