Confirm
2,242
edits
Changes
copied from 2017-01-10 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=24&month=1&year=2017&hour=13&min=0&sec=0&p1=0 24 January, 2017, 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]]
* Participants (in order of appearance):
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** '''TBD'''
=== Special agenda from the last meeting (for reference) ===
==== Release Planning next release ====
* Mozilla plans to remove XUL and classic extensions by the end of 2017. While it is still unclear if the time table is realistic the future outlook is bleak.
* It is unclear if the current SeaMonkey developer team can fix the upcoming build breaks fast enough to do regular releases.
* SeaMonkey 2.50a1 (FF 53) is building but this may change at any time. l20n is planned for FF 53 and might disrupt l10n building again.
* The consensus seems to be to do a ESR 52 cycle for the next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility.
* Thunderbird has been ESR only since the beginning of the train model. The biggest obstacle/restriction is that no string changes are allowed.
* Doing a 2.49 ESR will give the developer team a breather to fix the upcoming breaks in the mozilla source tree.
* Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine.
==== Release Planning mid/long term ====
* Mid/Long term release planning was not discussed because of time constraints. It will be put on the agenda of the next status meeting.
* It was suggested that we set up own builders to become more independent of Mozilla. '''adriank''' already has a working build system based on Jenkins. '''Ratty''' and '''ewong''' would like to set up one based on buildbot. No decision needed right now but this needs to be worked out.
* A new build system should provide try builds and should us also enable doing automated tests again.
=== 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'''
* Mozilla plans to check in l20n early in the Firefox 53 release cycle. Unclear what this means for comm-central and the build configs. Needs to be monitored.
** in light of this and [[#Release_Train|other changes in 52+]], releasing 2.49.x off 52 ESR becomes an increasingly attractive option
* Google announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in {{bug|1167038}}.
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong has a Google API key (stating that for Geolocation service). Safe Browsing keys are on the builders according to ewong. The build configs are currently being reviewed.
* '''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 prepare the final draft of the project areas this week.
* '''frg''' suggests a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
** '''IanN''' suggests doing small patches which are easier to review.
* '''frg''' thinks we should try to get our own builders.
** where, which build environment, how to cover associated costs?
** 2.46 release: improvise with contributed builds?
* —
'''CLOSED'''
* What to do about 0-day {{bug|1321066}}:
** Preferably release 2.46 with the fix, just would have to land on m-r relbranch;
** <s>alternatively, spin a 2.40.1 if patch applies and doesn't cause any other issues.</s> ''(2.46 released)''
* —
=== 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 on the loaner works.
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule. Currently no clear overview available.
** Note for this session: due to some weird horkage on the master (my bad), the master had to be restarted(and by restarted, I meant the buildbot process and not the system). The following status isn't updated as I don't have actual information as to the actual status. (Though, I know for sure Trunk is green as that's the only tree that was built since I had restarted the master).
* CZ langpacks seem to be disabled by default, so that needs to be sorted.
* DOMi still needs to be sorted.
* The block lists are no longer updated. Covered by {{bug|1315878}}.
* [10th January 2016]
** 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 (though OSX64 is backlogged, but it should be green).
*** See {{bug|1319091}} for current breakages.
** [comm-aurora]:
*** Linux*: Green
*** OSX64: Orange/Green
*** See {{bug|1313304}} for current breakages.
** [comm-beta]
*** Pretty much Green/Orange.
** [comm-release]:
*** Green/Orange.
* 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 any time soon.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine. He is still unable to set a timeframe for the next release. The moco build system is constantly changing. The MAC builders can be updated to OSX 10.9. He needs to consult with '''Callek''' first about this. He has trouble building the Windows version on the loaner.
** 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 VS2015 would likely solve this and other bustages. '''Ewong made substantial progress here and building works on the loaner'''.
** There are also some upcoming changes to l10n build system in Q1 2015 ({{bug|1107635}}).
** 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}}
** Issues with this release:
*** l10n problem is tracked in ({{bug|1231349}}).
*** Chatzilla and DOMi repack problems are also tracked in {{Bug|1315552}}.
*** Wrong Lightning version in 2.46 build 6 Release Candidate. See {{Bug|1309372}}. '''landed on trunk'''
** Release notes in {{Bug|1302639}} need helping hands.
** Setting the default search engine no longer works. This is covered in {{Bug|1265881}} and will not be fixed for 2.46. It needs to be added to the release notes.
** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists.
** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46.
** gtk3 will be disabled in the release build in {{Bug|1213152}}.
*** There are at least two problems with gtk3 builds which can not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}).
*** 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. Probably a meta bug for gtk3 compatibility should be created.
** '''frg''' suggests shipping 2.46 without cZ and DOMi if the l10n problems can not be fixed in time.
*** likely to happen for all locales including (en-US)
* ewong: Suggests the following:
** Officially release a linux64 build (incl. tests)
*** Start with 2.50 (or if we don't make it, 2.51) 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 with 2.51 (we need to iron out the build issues, though right now, having just finished a W64 build, we might be able to have it available with 2.50; but I don't know how the tests are going to work(though this will need to wait).
*** Currently tracked by {{bug|482143}}.
* Backup plan in case we need it is to do some releases off comm-esr52. These would be 2.49.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break 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/].
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
** Thunderbird solved l10n issues with their 49.0 beta, hopefully that procedure is transplantable to SeaMonkey.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th).
** 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}}
=== Extensions and Plugins Compatibility Tracking ===
* '''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.
* '''Firefox plans to disallow all NPAPI plugins other than Flash with Gecko 52''' ({{bug|1269807}}, [https://www.fxsitecompat.com/en-CA/docs/2015/plug-in-support-will-be-dropped-by-the-end-of-2016-except-flash/], [https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/]).
** builds will receive a run-time check ignoring (i.e., not loading) all plugins other than Flash.
*** exception is the m-esr52 branch which will not perform this check (other than Win64 platforms per {{bug|1165981}}).
*** in Gecko 52 ''only'', this will be controlled by a pref plugin.load_flash_only which is planned to be removed with Gecko 53.
**** {{bug|1308273}} flips that pref to allow all plugins in 2.49 at least. '''(landed)'''
** SeaMonkey might release a 2.49 ESR build based on FF 52 ESR code. Nothing decided yet.
** any workarounds or code in dom/plugins specific to other plugins may be subsequently removed.
* DOMi langpacks aren't working. Chatzilla langpacks show as disabled on a new profile.
** IanN has locale merge working for Chatzilla. He will be working on the DOMi repack issues tonight.
** See also {{Bug|652063}} (Enable localized ChatZilla builds).
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* '''Addons are now compatible by default. The code in the addon manager that complains about incompatible version numbers has been removed. This should reduce the friction of installing older addons.'''
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] (outdated), [http://addonconverter.fotokraina.com/compatibility/ alternative list started] (currently Rainer Bielefeld is the only active maintainer)
* 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].
** 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] extension has been updated on June 28 and again (but Beta) on July 2. [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 works with them ''(or at least with the "latest" 2016-06-25 tinderbox-build)''. 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.
* Some warning messages might be caused by improper toolkit checking for disabled signing. See {{Bug|1291749}}.
* 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 are currently being 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] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 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_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (16)
==== 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.
* 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}}.
** Firefox has changed the styles of several Toolkit pages to their "in-content" designs which however look very out of place in our current classic and modern themes.
**** 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.
*** '''about:addons''' yet to come {{Bug|1222817}}
*** 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.
** 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. Currently being worked on by IanN.
** '''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'''.
* [Ratty] made some progress to fix {{bug|1222817}} - Restore about:addons UI (Addons Manager) to old appearance. He found some useful ideas from the CSS in https://addons.mozilla.org/en-US/seamonkey/addon/classicish-addon-manager/ but currently doesn't have the time to continue.
* {{Bug|1300198}} Move list.txt over to JSON once bug 1276739 will likely break search engines and needs to be looked at.
* [frg] suggested to match SeaMonkeys minor version number with then one from Firefox in a future release. This need to be looked into first because some external releng or other stuff might rely on the -3 version offset.
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion.
* [ewong] stated that SeaMonkey needs to move to balrog which is the the new updates server/format to do a future 2.47 release.
* [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 after the status meeting.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 43 new, 42 fixed, 22 triaged.
* higher triaging effort, substantial number of new bugs filed after the 2.46 release.
[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 49 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 14 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)]
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
** {{Bug|1269807}} Remove support for all NPAPI plugins (except Flash)
*** for Gecko 52+ retail, ''not'' for 52 ESR branch
** Gecko 51 will be the last version supporting Windows XP and probably Vista too.
*** This is tracked in {{bug|1130266}}. Support for it is moved to ESR 52 in {{bug|1303827}}. The plan was approved by Mozilla management.
*** SeaMonkey 2.48 (or 2.49 if built from ESR) and Firefox 51 will be the ''last'' retail versions running on WinXP and Vista.
*** At the current time getting 2.46 out is priority one. After release there are several options open which have been discussed. What to do will be decided later:
**** Do ESR and regular releases. Due to a shortage of manpower participants are not sure if this is feasible.
**** Drop XP support with providing an unofficial ESR release optionally.
**** Switch to ESR releases only. Until now only SeaMonkey 2.35 has been built from the ESR branch. After 2.46 a trial 2.42.x / ESR 45 might be built to see if this still works.
**** We need to decide later. '''frg''' suggests doing a separate status meeting for this when Mozillas plans become clearer.
**** Several bugs are already in place to remove XP and Vista support from m-c 53+ completly. Seamonkey will not be able to back them out so an ESR would be a must if we still want to support them.
** {{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.
* 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}}.
** System Requirements needs an update. Tracked in {{Bug|1208822}}.
* The website and wiki are outdated. '''InvisibleSmiley''' no longer maintains the website. For 2.46 the website needs to be updated.
** {{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.
=== Roundtable - Personal Status Updates ===
'''Ratty or IanN will handle review requests.'''
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 ====
Looking 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].
==== sgautherie ====
==== stefanh ====
==== tonymec ====
<!-- scratchpad for next meeting, 2016-12-20. Please cut & paste, then uncomment.
* Triage: Business as usual but maybe getting lazy.
<div style="font-family: monospace; font-size: smaller; font-style: italic; margin-left: 0.75in">
My mother she is working, she is working very hard<br>
But every time she looks for me I'm sleeping in the yard.<br>
My mother thinks I'm lazy, and maybe she is right:<br>
I'll go to work MAÑANA but I gotta sleep tonight.<br>
MAÑANA, MAÑANA, MAÑANA is soon enough for me.</div>
* New Bugzilla search: [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=All%20%22doorhanger%22%20bugs%20this%20month&sharer_id=104443 All "doorhanger" bugs this month] — for any Product::Component, but won't (yet?) catch bugs whose Summary says "notification" but not "doorhanger".
-->
=== Any other business? ===
* Status meeting times/days.
'''SeaMonkey Meeting Details'''
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=24&month=1&year=2017&hour=13&min=0&sec=0&p1=0 24 January, 2017, 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]]
* Participants (in order of appearance):
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** '''TBD'''
=== Special agenda from the last meeting (for reference) ===
==== Release Planning next release ====
* Mozilla plans to remove XUL and classic extensions by the end of 2017. While it is still unclear if the time table is realistic the future outlook is bleak.
* It is unclear if the current SeaMonkey developer team can fix the upcoming build breaks fast enough to do regular releases.
* SeaMonkey 2.50a1 (FF 53) is building but this may change at any time. l20n is planned for FF 53 and might disrupt l10n building again.
* The consensus seems to be to do a ESR 52 cycle for the next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility.
* Thunderbird has been ESR only since the beginning of the train model. The biggest obstacle/restriction is that no string changes are allowed.
* Doing a 2.49 ESR will give the developer team a breather to fix the upcoming breaks in the mozilla source tree.
* Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine.
==== Release Planning mid/long term ====
* Mid/Long term release planning was not discussed because of time constraints. It will be put on the agenda of the next status meeting.
* It was suggested that we set up own builders to become more independent of Mozilla. '''adriank''' already has a working build system based on Jenkins. '''Ratty''' and '''ewong''' would like to set up one based on buildbot. No decision needed right now but this needs to be worked out.
* A new build system should provide try builds and should us also enable doing automated tests again.
=== 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'''
* Mozilla plans to check in l20n early in the Firefox 53 release cycle. Unclear what this means for comm-central and the build configs. Needs to be monitored.
** in light of this and [[#Release_Train|other changes in 52+]], releasing 2.49.x off 52 ESR becomes an increasingly attractive option
* Google announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in {{bug|1167038}}.
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong has a Google API key (stating that for Geolocation service). Safe Browsing keys are on the builders according to ewong. The build configs are currently being reviewed.
* '''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 prepare the final draft of the project areas this week.
* '''frg''' suggests a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
** '''IanN''' suggests doing small patches which are easier to review.
* '''frg''' thinks we should try to get our own builders.
** where, which build environment, how to cover associated costs?
** 2.46 release: improvise with contributed builds?
* —
'''CLOSED'''
* What to do about 0-day {{bug|1321066}}:
** Preferably release 2.46 with the fix, just would have to land on m-r relbranch;
** <s>alternatively, spin a 2.40.1 if patch applies and doesn't cause any other issues.</s> ''(2.46 released)''
* —
=== 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 on the loaner works.
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule. Currently no clear overview available.
** Note for this session: due to some weird horkage on the master (my bad), the master had to be restarted(and by restarted, I meant the buildbot process and not the system). The following status isn't updated as I don't have actual information as to the actual status. (Though, I know for sure Trunk is green as that's the only tree that was built since I had restarted the master).
* CZ langpacks seem to be disabled by default, so that needs to be sorted.
* DOMi still needs to be sorted.
* The block lists are no longer updated. Covered by {{bug|1315878}}.
* [10th January 2016]
** 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 (though OSX64 is backlogged, but it should be green).
*** See {{bug|1319091}} for current breakages.
** [comm-aurora]:
*** Linux*: Green
*** OSX64: Orange/Green
*** See {{bug|1313304}} for current breakages.
** [comm-beta]
*** Pretty much Green/Orange.
** [comm-release]:
*** Green/Orange.
* 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 any time soon.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine. He is still unable to set a timeframe for the next release. The moco build system is constantly changing. The MAC builders can be updated to OSX 10.9. He needs to consult with '''Callek''' first about this. He has trouble building the Windows version on the loaner.
** 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 VS2015 would likely solve this and other bustages. '''Ewong made substantial progress here and building works on the loaner'''.
** There are also some upcoming changes to l10n build system in Q1 2015 ({{bug|1107635}}).
** 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}}
** Issues with this release:
*** l10n problem is tracked in ({{bug|1231349}}).
*** Chatzilla and DOMi repack problems are also tracked in {{Bug|1315552}}.
*** Wrong Lightning version in 2.46 build 6 Release Candidate. See {{Bug|1309372}}. '''landed on trunk'''
** Release notes in {{Bug|1302639}} need helping hands.
** Setting the default search engine no longer works. This is covered in {{Bug|1265881}} and will not be fixed for 2.46. It needs to be added to the release notes.
** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists.
** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46.
** gtk3 will be disabled in the release build in {{Bug|1213152}}.
*** There are at least two problems with gtk3 builds which can not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}).
*** 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. Probably a meta bug for gtk3 compatibility should be created.
** '''frg''' suggests shipping 2.46 without cZ and DOMi if the l10n problems can not be fixed in time.
*** likely to happen for all locales including (en-US)
* ewong: Suggests the following:
** Officially release a linux64 build (incl. tests)
*** Start with 2.50 (or if we don't make it, 2.51) 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 with 2.51 (we need to iron out the build issues, though right now, having just finished a W64 build, we might be able to have it available with 2.50; but I don't know how the tests are going to work(though this will need to wait).
*** Currently tracked by {{bug|482143}}.
* Backup plan in case we need it is to do some releases off comm-esr52. These would be 2.49.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break 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/].
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
** Thunderbird solved l10n issues with their 49.0 beta, hopefully that procedure is transplantable to SeaMonkey.
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th).
** 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}}
=== Extensions and Plugins Compatibility Tracking ===
* '''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.
* '''Firefox plans to disallow all NPAPI plugins other than Flash with Gecko 52''' ({{bug|1269807}}, [https://www.fxsitecompat.com/en-CA/docs/2015/plug-in-support-will-be-dropped-by-the-end-of-2016-except-flash/], [https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/]).
** builds will receive a run-time check ignoring (i.e., not loading) all plugins other than Flash.
*** exception is the m-esr52 branch which will not perform this check (other than Win64 platforms per {{bug|1165981}}).
*** in Gecko 52 ''only'', this will be controlled by a pref plugin.load_flash_only which is planned to be removed with Gecko 53.
**** {{bug|1308273}} flips that pref to allow all plugins in 2.49 at least. '''(landed)'''
** SeaMonkey might release a 2.49 ESR build based on FF 52 ESR code. Nothing decided yet.
** any workarounds or code in dom/plugins specific to other plugins may be subsequently removed.
* DOMi langpacks aren't working. Chatzilla langpacks show as disabled on a new profile.
** IanN has locale merge working for Chatzilla. He will be working on the DOMi repack issues tonight.
** See also {{Bug|652063}} (Enable localized ChatZilla builds).
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* '''Addons are now compatible by default. The code in the addon manager that complains about incompatible version numbers has been removed. This should reduce the friction of installing older addons.'''
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] (outdated), [http://addonconverter.fotokraina.com/compatibility/ alternative list started] (currently Rainer Bielefeld is the only active maintainer)
* 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].
** 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] extension has been updated on June 28 and again (but Beta) on July 2. [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 works with them ''(or at least with the "latest" 2016-06-25 tinderbox-build)''. 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.
* Some warning messages might be caused by improper toolkit checking for disabled signing. See {{Bug|1291749}}.
* 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 are currently being 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] (1)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 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_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (16)
==== 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.
* 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}}.
** Firefox has changed the styles of several Toolkit pages to their "in-content" designs which however look very out of place in our current classic and modern themes.
**** 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.
*** '''about:addons''' yet to come {{Bug|1222817}}
*** 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.
** 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. Currently being worked on by IanN.
** '''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'''.
* [Ratty] made some progress to fix {{bug|1222817}} - Restore about:addons UI (Addons Manager) to old appearance. He found some useful ideas from the CSS in https://addons.mozilla.org/en-US/seamonkey/addon/classicish-addon-manager/ but currently doesn't have the time to continue.
* {{Bug|1300198}} Move list.txt over to JSON once bug 1276739 will likely break search engines and needs to be looked at.
* [frg] suggested to match SeaMonkeys minor version number with then one from Firefox in a future release. This need to be looked into first because some external releng or other stuff might rely on the -3 version offset.
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion.
* [ewong] stated that SeaMonkey needs to move to balrog which is the the new updates server/format to do a future 2.47 release.
* [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 after the status meeting.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 43 new, 42 fixed, 22 triaged.
* higher triaging effort, substantial number of new bugs filed after the 2.46 release.
[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 49 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 14 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)]
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
** {{Bug|1269807}} Remove support for all NPAPI plugins (except Flash)
*** for Gecko 52+ retail, ''not'' for 52 ESR branch
** Gecko 51 will be the last version supporting Windows XP and probably Vista too.
*** This is tracked in {{bug|1130266}}. Support for it is moved to ESR 52 in {{bug|1303827}}. The plan was approved by Mozilla management.
*** SeaMonkey 2.48 (or 2.49 if built from ESR) and Firefox 51 will be the ''last'' retail versions running on WinXP and Vista.
*** At the current time getting 2.46 out is priority one. After release there are several options open which have been discussed. What to do will be decided later:
**** Do ESR and regular releases. Due to a shortage of manpower participants are not sure if this is feasible.
**** Drop XP support with providing an unofficial ESR release optionally.
**** Switch to ESR releases only. Until now only SeaMonkey 2.35 has been built from the ESR branch. After 2.46 a trial 2.42.x / ESR 45 might be built to see if this still works.
**** We need to decide later. '''frg''' suggests doing a separate status meeting for this when Mozillas plans become clearer.
**** Several bugs are already in place to remove XP and Vista support from m-c 53+ completly. Seamonkey will not be able to back them out so an ESR would be a must if we still want to support them.
** {{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.
* 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}}.
** System Requirements needs an update. Tracked in {{Bug|1208822}}.
* The website and wiki are outdated. '''InvisibleSmiley''' no longer maintains the website. For 2.46 the website needs to be updated.
** {{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.
=== Roundtable - Personal Status Updates ===
'''Ratty or IanN will handle review requests.'''
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 ====
Looking 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].
==== sgautherie ====
==== stefanh ====
==== tonymec ====
<!-- scratchpad for next meeting, 2016-12-20. Please cut & paste, then uncomment.
* Triage: Business as usual but maybe getting lazy.
<div style="font-family: monospace; font-size: smaller; font-style: italic; margin-left: 0.75in">
My mother she is working, she is working very hard<br>
But every time she looks for me I'm sleeping in the yard.<br>
My mother thinks I'm lazy, and maybe she is right:<br>
I'll go to work MAÑANA but I gotta sleep tonight.<br>
MAÑANA, MAÑANA, MAÑANA is soon enough for me.</div>
* New Bugzilla search: [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=All%20%22doorhanger%22%20bugs%20this%20month&sharer_id=104443 All "doorhanger" bugs this month] — for any Product::Component, but won't (yet?) catch bugs whose Summary says "notification" but not "doorhanger".
-->
=== Any other business? ===
* Status meeting times/days.
