Meeting Notes Meetings notes from the Mozilla community

26-April-2016

SeaMonkey: 2016-04-26

Filed under: Posts — Tags: — Jesper Kristensen @ 11:00 pm

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • Ewongwho got the Linux32/Linux64 nightlies out just in time for the central->aurora release train.

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

  • Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
    • Mcsmurf will generate an updated key and pass it to Ewong who will then upload it to our build machines.
    • Update from Ewong: Hasn’t received the key from mcsmurf yet.
  • IanN to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
    • TODO: Add Adrian Kalla to RelEng team.
  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

Previously on Agents of SHIELD:

A) create an instance of the current Buildbot-based system specifically for Thunderbird; or
B) port Thunderbird to a new system using Taskcluster and Amazon Machine Images (AMIs).
We believe porting Thunderbird to a new system is the best plan of these two by a wide margin. Buildbot is old and patched and not easy to understand. That system would require physical rather than virtual machines. Firefox is also moving to Taskcluster, which is a new build and release automation system being written for Mozilla particularly to meet the needs of products with complex requirements like Firefox and Thunderbird. We imagine the cost of operating a Taskcluster system, in both money and person-hours, would be much less. This is good for Thunderbird in the long term, as it makes the system much more manageable.
    • Callek thinks that a (scaled down) Taskcluster system would be appropriate for SeaMonkey. We have been piggy-backing on Mozilla infrastructure since the begining. If/When the Thunderbird Project gets it’s own infrastructure, it makes sense for SeaMonkey to tag along. One problem is – does Thunderbird want us tagging along? The SeaMonkey project does have the financial resources to pay for our share of AMI.
  • Chatzilla locale generation: Frg investigating why the L10n xpi isn’t being added into the installer.

Routine reports:

  • Notes:
    • Comm-Central just broke. nsRunnable has benn renamed bug 1265927. MailNews bug 1265927 has been opened to fix this problem. Everything else compiles.
    • comm-* branches are still closed due to the merges. Windows32 and OSX are still not building though.
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until January at earliest any time soon.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2015 would likely solve this and other bustages. Ratty’ is currently reviewing these and other patches to make this happen.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.45a1 dated 8-Mar-2016 for W32; 2.46a1 dated 26-Apr-2016 for L32 & L64, and 2.43a1 dated 6-Jan-2016 for Mac. ** bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • 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.
  • [26th April 2016]
    • [*All Trees*]
    • [comm-central]
    • [comm-beta, comm-release]
      • Linux*: Busted. Waiting for review on patches for c-b and c-r from bug 1190773.
      • OSX64: busted due to bug 1260362.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.40 is out.
  • We are skipping SeaMonkey 2.41 and 2.42 and going directly to 2.43 betas.
  • Backup plan in case we need it is to do some releases off comm-esr45. These will be 2.42.x releases.
    • [frg] I used 2.42 too since Beta 1. It is stable as 2.43, I backported Data Manager and a few other fixed bugs like Safe Browsing.
    • Need to check how to port L10n changes from SeaMonkey 2.43 to comm-esr. bug 1240738 tracks l10n changes that need uplifting to 2.42.x in case we build from 45.x ESR.
  • Merges were performed as scheduled on April 25 (mozilla-beta → release: April 15).
    • comm-release default has moved to SM 2.43.
      • We need is land bug 1266052 and bug 1265246 on comm-release in order to build 2.43.
      • If possible we should also land bug 1265181 and bug 1265326 but there is some bit rot preventing these from applying properly. “Please apply patches from bug 1260697 and bug 1265170 first.”
    • comm-release and mozilla-release are now on 46.0.
    • comm-esr45 and mozilla-esr45 are current in preparation of TB 45.1 release.
    • lots of comm-beta bug fixes landed on THUNDERBIRD451b1_2016042214_RELBRANCH (for 45.1, mirroring comm-esr45) but not the default branch
      • changesets landing on relbranch only which contain non-mail/non-calendar diffs: ff7bcfb79ba3, 83fd96b13074, 3497b6426758, ff8a2e5bcaaf, 2242b156ded5
      • not entirely clear how this will affect building 2.42/2.43 off comm-release after the merge
      • Ratty: After the merge on 2016-04-25 comm-beta is now at Gecko 47b which corresponds to SeaMonkey 2.44b so everything should match up. Everything in THUNDERBIRD451b1_2016042214_RELBRANCH should be on the BETA_BASE_20160425 tag.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings (outdated), altertative list started (currently Rainer Bielefeld is the only active maintainer)
  • There is still no matching Lightning version for 2.43 and since Thunderbird skipped the TB 46.0 beta, there may not be any (Lightning 4.8b1).
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is currently shipping Lightning with Thunderbird. IanN is working on shipping Lightning with SeaMonkey. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (5)
targeted (2)
fixed (14)

2.Next

  • We need someone to work on porting sync 2.0 over to replace legacy sync code. Frg might look into this if he doesn’t have anything more urgent to work on.
    See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages (have patches need review and check-in):
    • —
  • Mozilla-central bugs that affect us:
    • 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.
      • about:config Fixed in SeaMonkey bug 1222816.
      • about:privatebrowsing Fixed in SeaMonkey [bug 1192276
        • Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • Affected pages that need to be fixed are about:addons [bug 1222817], about:support [bug 1222818] (looks ok in Modern but painful in the Default theme).
      • 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. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673) WONTFIX.
      • Rsx11m filed bug 1267631 Update the SSL/TLS Preference Pane once TLS 1.3 is implemented and ready for prime time.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 17 new, 16 fixed, 9 triaged.

  • medium triaging effort, below-average number of new bugs files.

Open reviews/flags:
60 review
5 super-review
2 ui-review
11 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
      • Toolkit Help Viewer bugs will be moved to the SeaMonkey product. This is tracked in bug 1243203.
      • Neil is AFK for the forseeable future so we need to plan to import the Help Viewer code to comm-central if they remove it before Neil can come around to fix things.
    • Remove debugQA from Seamonkey or overhaul it removing obsolete items. See discussion in bug 1258226
    • 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
  • 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.
      • No sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported.
      • No clear statements by the Firefox drivers, bug has been restricted for comments since.
      • Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
      • See bsmedberg’s post #14, targeted for Gecko 49 (April 2016).
      • May prohibit Modern theme being shipped with or installed in SeaMonkey.
      • Removal is “decided” without any clear alternative envisioned.
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ? — Tonymec (talk) 13:56, 7 October 2015 (PDT)
    • On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.
    • How are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.
    • Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)
    • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

Roundtable – Personal Status Updates

Neil has a new job and doesn’t have any time to devote to SeaMonkey. Please re-direct review requests to Ratty or IanN who will redirect elsewhere if needed.

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

ewong

frg

Waiting for review / branch check in or feedback:

  • bug 1055954 popup exceptions are not added. Updated patch for popup menu.
  • bug 1223741 Updating to 2.39B allow images not working. Follow up Data Manager change to allow chrome, files and other schemes to not cause errors still needs some work and will get a new bug number.
  • bug 1224437 No “Publishing completed” status after green tick, publishing does not terminate
  • bug 1265130 Bug 1265130 bustage in ‘make package’ for extensions due to removal of MOZ_OMNIJAR. Ratty and I are in disagreement/unsure which path to take. I would say remove the variable and the flat packing code. TB and FF are doing the same. 2.45+ suite will not build without a fix for this.

Working on:

  • bug 1258226 Remove debugQA from SeaMonkey. Input please if this should be up for reviewed if we should keep debugQA in it’s current state. A little on the back burner but not forgotten
  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrian Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.
  • bug 1256714 Aero Peek not working. Digged deeper into it. Works for everything but websites with a zoom factor < 100%. Might be a backend bug with scale.

Titbits:

  • Will try to work on Sync next as promised.

Other things on my mind:

  • –enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013/VS2015 it optimizes for size. Resulting O2 Windows build feels a lot snappier.
  • bug 1244467 Localized Builds: ChatZilla language pack missing from SeaMonkey installer package will not be fixed by bug 1210791. mozmake installer under Windows includes the l10n xpi in local builds.
  • When looking in Bugzilla what to do next I found a lot of in my eyes obsolete bugs in a short time. Who can close them. Tracking them in a meta bug? A little on the backburner too but also not forgotten.
Comment from 03/29: I am working on this problem. We have lots of UNCONFIRMED Bugs, many of them old /obsolete. But in my systematic review (may be 3 … 5 each week) I find (approximately) 25% of these old bugs real bugs, half of them Core half of them really SeaMonkey bugs. With this speed review still will take 2 more years or so, but I think it’s better than a mass-close. — Rrbd (talk) 10:53, 29 March 2016 (PDT)

Some more precise statistics here in the unofficial blog. — Rrbd (talk) 22:31, 29 March 2016 (PDT)

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Rainer Bielefeld

I will not participate.

currently working on
ToDos
  • I will submit a bigger number of Bugs or enhancement requests for SeaMonkey Help and contribute fixes, hoping to find some new volunteers to add fixes to Help files.

Ratty

Fixed:

  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1259928 “View Selection Source” throws TypeError: args is null Source File: chrome://global/content/viewPartialSource.js.
  • bug 1261685 All Bookmarks functionality broken due to Toolkit bug 1257599 which renamed ‘Unsorted Bookmarks’ into ‘Other Bookmarks’.

In Progress:

  • Not much. Concentrating on doing reviews this current cycle.

TODO:

  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1116223 Thunderbird: Move overrides to default theme chrome.manifest.

Other stuff:

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

rsx11m

Pushed to comm-central,
landed on comm-aurora (before the merge) and comm-esr45,
waiting for comm-release approval:

  • bug 1265246 Move Thunderbird-specific change of editor.CR_creates_new_p default from composer.js to all-thunderbird.js override.
    • would still need to land on SeaMonkey’s release branch on comm-release for 2.42 and/or 2.43, unless 2.42.1 is the next release off comm-esr45.
    • fall-out from bug 330891 where Thunderbird changed composer.js default, patch reverts that change

Pushed to comm-central (before the merge):

Waiting for reviews:

  • bug 1265534 Make editor.CR_creates_new_p work for Mail & News composition as well
    • adopts new “compose HTML in Paragraph mode” feature from bug 330891 without making it the default

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-04-26&oldid=1129423”

12-April-2016

SeaMonkey: 2016-04-12

Filed under: Posts — Tags: — Jesper Kristensen @ 11:00 pm

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

  • —

OPEN

  • Google api key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
    • Mcsmurf will generate an updated key and pass it to Ewong who will then upload it to our build machines.
  • IanN to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
    • TODO: Add Adrian Kalla to RelEng team.
  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

Previously on Buffy The Vampire Slayer:

  • Followup to discussion in previous meeting notes
  • Adriank thinks we need an *own* build infra separate from MoCo. What is needed is buildbot (Adrian uses Jenkins), a Windows, Linux, and OSX virtual machine.
  • Ewong and Ratty discussed setting up an instance of Treeherder on our own hardware but couldn’t decide how to have a secure connection to our builders on MoCo’s infrastructure.
    • [Ratty thinks that] We could rent some colo Mac Mini servers, startup some OSX VMs one of which could run treeherder and a buildbot master. This way we could get some up to date coverage on OSX builds.
    • e.g. Macminicolo
  • Chatzilla locale generation: Frg investigating why the L10n xpi isn’t being added into the installer.

Routine reports:

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until January at earliest any time soon.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 VS2015 would likely solve this and other bustages. frg 03/27: moot point to do it. m-c switched to VS2015 via tooltool on 03/25. See my section.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.45a1 dated 8-Mar-2016 for W32, L32 & L64, and 2.43a1 dated 6-Jan-2016 for Mac. ** bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • 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.
  • [12th April 2016]
    • [*All Trees*]
      • Aside for the following specific tree bustages, we are generally busted for all trees due to the fact that our rsa ssh key needs to be changed (currently waiting), so uploading to archive.mo is busted (due to our old key being revoked/removed). Callek is working on this.
    • [comm-central]
    • [comm-aurora, comm-beta]
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.40 is out.
  • We are skipping SeaMonkey 2.41 and 2.42 and going directly to 2.43 betas.
  • Backup plan in case we need it is to do some releases off comm-esr45. These will be 2.42.x releases.
    • [frg] I used 2.42 too since Beta 1. It is stable as 2.43, I backported Data Manager and a few other fixed bugs like Safe Browsing.
    • Need to check how to port L10n changes from SeaMonkey 2.43 to comm-esr. bug 1240738 tracks l10n changes that need uplifting to 2.42.x in case we build from 45.x ESR.
  • Next merges are now scheduled for April 25 (beta → release: April 18).
    • comm-release default is moving to SM 2.43.
    • comm-release and mozilla-release will be on 46.0.
    • comm-esr45 and mozilla-esr45 are current in preparation of TB 45.0/.1 release.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings (outdated), altertative list started (currently Rainer Bielefeld is the only active maintainer)
  • Lightning betas are up for 2.42 (4.7b3), but not yet for 2.43 (4.8b1).
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is currently shipping Lightning with Thunderbird. IanN is working on shipping Lightning with SeaMonkey. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (2)
fixed (14)

2.Next

  • We need someone to work on porting sync 2.0 over to replace legacy sync code. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages (have patches need review and check-in):
    • bug 1259928 “View Selection Source” throws TypeError: args is null Source File: chrome://global/content/viewPartialSource.js.
    • bug 1261685 All Bookmarks functionality broken due to Toolkit Bug 1257599 which renamed ‘Unsorted Bookmarks’ into ‘Other Bookmarks’
  • Mozilla-central bugs that affect us:
    • Introduction of a cloud-based certificate revocation list system for blocklists bug 1227956. Fixed by rsx11m in bug 1259947).
    • Changes to Safe Browsing. Frg has a patch ready for check-in in bug 1250600 .
    • 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.
      • already affected: config.xul for about:config, Will be fixed in SeaMonkey bug 1222816.
      • 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
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite. 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. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

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

  • good triaging effort, below-average number of new bugs files.

Open reviews/flags:
65 review
5 super-review
1 ui-review
12 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
      • Toolkit Help Viewer bugs will be moved to the SeaMonkey product. This is tracked inbug 1243203.
      • Neil is AFK for the forseeable future so we need to plan to import the Help Viewer code to comm-central if they remove it before Neil can come around to fix things.
    • Remove debugQA from Seamonkey or overhaul it removing obsolete items. See discussion in bug 1258226
    • 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
  • 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.
      • No sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported.
      • No clear statements by the Firefox drivers, bug has been restricted for comments since.
      • Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
      • See bsmedberg’s post #14, targeted for Gecko 49 (April 2016).
      • May prohibit Modern theme being shipped with or installed in SeaMonkey.
      • Removal is “decided” without any clear alternative envisioned.
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ? — Tonymec (talk) 13:56, 7 October 2015 (PDT)
    • On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.
    • How are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.
    • Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)
    • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

Roundtable – Personal Status Updates

Neil has a new job and doesn’t have any time to devote to SeaMonkey. Please re-direct review requests to Ratty or IanN who will redirect elsewhere if needed.

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

ewong

  • Working on:
    • bug 1190773 – Tooltool revamp
    • a lot of other firefights, but currently blocked on the need to have the ssh key updated.

frg

I might not be able to attend. 50/50 chance.

Waiting for review / branch check in or feedback:

  • bug 1055954 popup exceptions are not added. Please review and let me know if it’s ok. Contains string changes. Would be great if this could be checked in in this cycle. Like the Data Manager changes contains string changes and so will/might affect third party themes.
  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Checked into c-c. Any chance it can go into c-a despite the string changes?
  • bug 1251368 SeaMonkey cookie code needs to be updated to take into account mozilla-central bug 1245184. Might work without checking bug 1188348 in first but not tested. 2.44 and up affected. Checked into c-c.
  • bug 1223741 Updating to 2.39B allow images not working.

Working on:

  • bug 1258226 Remove debugQA from SeaMonkey. Input please if this should be up for reviewed if we should keep debugQA in it’s current state. A little on the back burner but not forgotten
  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrian Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.
  • bug 1223741 Already working on Data Manager changes to allow chrome, files and other schemes to not cause errors.
  • bug 1263252 Update SeaMonkey cookie code for mozilla-central Bug 1259169 [nsICookieManager::remove() should be back-compatible. Ready for review but mozilla bug backed out for now.

Titbits:

  • bug 1210791 Get rid of XULPPFLAGS in ChatZilla was checked in. SEA2_42_RELBRANCH needs a new tag to the current default changeset so that the l10n xpi might be generated.
  • Will try to work on Sync next as promised.

Other things on my mind:

  • –enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013/VS2015 it optimizes for size. Resulting O2 Windows build feels a lot snappier.
  • SeaMonkey compiles fine with VS2015 Update 2 with Windows 10 SDK 10.0.10586.15 and mozbuild 2.2.0. x86 builds produced still work fine under Windows XP SP3. x64 build is stable for daily use in my eyes (same with VS2013). The VS2015 upgrade installer is a piece of… Full ISO is available here: http://download.microsoft.com/download/f/d/c/fdce5d40-87d3-4bd6-9139-2a7638b96174/vs2015.2.com_enu.iso
  • VS2015 c-b and c-a builds broken by bug 1256541. Will likely not be fixed but easy workaround for local builds available.
  • bug 1244467 Localized Builds: ChatZilla language pack missing from SeaMonkey installer package will not be fixed by bug 1210791. mozmake installer under Windows includes the l10n xpi in local builds.
  • Aero Peek is broken in c-b and up see bug 1256714. Quick fix in the bug but not complete. Further porting and a bugfix for sites with different zoom levels needed. If no one takes it until I find some time I will try to fix it.
  • When looking in Bugzilla what to do next I found a lot of in my eyes obsolete bugs in a short time. Who can close them. Tracking them in a meta bug? A little on the backburner too but also not forgotten.
Comment from 03/29: I am working on this problem. We have lots of UNCONFIRMED Bugs, many of them old /obsolete. But in my systematic review (may be 3 … 5 each week) I find (approximately) 25% of these old bugs real bugs, half of them Core half of them really SeaMonkey bugs. With this speed review still will take 2 more years or so, but I think it’s better than a mass-close. — Rrbd (talk) 10:53, 29 March 2016 (PDT)

Some more precise statistics here in the unofficial blog. — Rrbd (talk) 22:31, 29 March 2016 (PDT)

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Rainer Bielefeld

I will not participate.

currently working on
  • DMOZ SeaMonkey related entries:
    • Review with low priority, including trying to get contact to site owners of listed web pages
  • Trying to help to repair problems with Add-ON Browsing for SeaMonkey caused by new AMO design:
  • QA, Bug confirming and so on as usual
You might want to discuss
  • SeaMonkey Project homepage maintenance
Performance currently needs improvement, contents of Page System Requirements (for example, see bug 1208822 – SeaMonkey System Requirements need update) is mortifying outdated. Due to Wiki Component Web pages has 2 peers: Justin Wood (:Callek) and Robert Kaiser (:KaiRo). But the peers are inactive, as this Bugzilla query shows that Jens Hatklak is the only active maintainer. That should be reflected in wiki and on Project Page, inactive peers should be removed. And there should be a strategy how to do the job with the available manpower: recruit volunteers and find a way how they can create drafts which can be integrated easily into the home page easily.

Ratty

Fixed:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • bug 1258955 Only small bottom area of DuckDuckGo logo icon shown in Search Sidebar and “Customize Toolbars”.
  • bug 1263262 Do not hide the menubar in the View Partial Source window [Toolkit].

Waiting for review:

  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1259928 “View Selection Source” throws TypeError: args is null Source File: chrome://global/content/viewPartialSource.js.
  • bug 1261685 All Bookmarks functionality broken due to Toolkit bug 1257599 which renamed ‘Unsorted Bookmarks’ into ‘Other Bookmarks’.

In Progress:

  • None

TODO:

  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1116223 Thunderbird: Move overrides to default theme chrome.manifest.

Other stuff:

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

rsx11m

Pushed to comm-central and comm-aurora:

  • bug 1259947 Add kinto-updater and OneCRL preferences to SeaMonkey.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-04-12&oldid=1127294”

29-March-2016

SeaMonkey: 2016-03-29

Filed under: Posts — Tags: — Jesper Kristensen @ 11:00 pm

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

  • IanN to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
  • —

OPEN

  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until January at earliest any time soon.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 VS2015 would likely solve this and other bustages. frg 03/27: moot point to do it. m-c switched to VS2015 via tooltool on 03/25. See my section.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.45a1 dated 8-Mar-2016 for W32, L32 & L64, and 2.43a1 dated 6-Jan-2016 for Mac. ** bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • 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.
  • [29th March 2016]
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.40 is out.
  • We are skipping SeaMonkey 2.41
  • Currently planning for 2.42.

Previously on Buffy The Vampire Slayer:

  • IanN suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta “release”. L10N Translations might be problematic however rsx11m says using ESR would be “safer” with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some “deal” to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that’s just simple patches such as label changes or adding a checkbox). rsx11m would go with {comm,mozilla}-esr45 and merge any “safe” patches from comm-beta but that may need some talking to l10n if string changes are involved.
  • Adriank thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
  • Frg: Chatzilla locale generation still broken. Frg and Adrian to deal with this.
  • SeaMonkey 2.40 final (tracking bug 1233615) was partially released March 14, 2016
  • Next merges are scheduled for April 18 (beta → release: April 11).
    • comm-release default is now on SM 2.42.
    • comm-release and mozilla-release are now on 45.0.
    • comm-esr45 and mozilla-esr45 are now current.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings (outdated), altertative list started (currently Rainer Bielefeld is the only active maintainer)
  • Lightning betas are up for 2.40, 2.41, and 2.42.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (2)
fixed (14)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla. To be fixed in bug 1210791 [checkin-needed]
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing. Frg has a patch ready for check-in in bug 1250600 .
    • Introduction of a cloud-based certificate revocation list system for blocklists bug 1227956. rsx11m has a patch in bug 1259947 mirroring TB changes (bug 1248557 and friends).
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, Will be fixed in SeaMonkey bug 1222816.
      • 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
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 36 new, 6 fixed, 6 triaged.

  • good triaging effort, Rainer Bielefeld has been busy filing and verifying bugs.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • If effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • No sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • No clear statements by the Firefox drivers, bug has been restricted for comments since
      • Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
      • See bsmedberg’s post #14, targeted for Gecko 49 (April 2016).
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.

Open reviews/flags:
64 review
5 super-review
1 ui-review
12 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ? — Tonymec (talk) 13:56, 7 October 2015 (PDT)
    • On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.
    • How are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.
    • Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)
    • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] More or less obsolete items removed 03/27. One l10n bug remaining but hopefully fixed soon.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

ewong

  • Working On:
    • bug 1190773 – backend change for tooltool process to support the new tooltool repo.
    • bug 1260993 – change our Linux* builders to use gcc 4.8.5.
    • waiting to see if the ‘fix’ for the 2.39 to 2.40 update for Win64 clients work.

frg

Waiting for review:

  • bug 1055954 popup exceptions are not added. Please review and let me know if it’s ok. Contains string changes.
  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Contains string changes and hopefully will not miss the next cycle. I am done here and any changes will be need to put in new bugs.
  • bug 1251368 SeaMonkey cookie code needs to be updated to take into account mozilla-central bug 1245184. Might work without checking bug 1188348 in first but not tested. 2.44 and up affected.
  • bug 1250600 Update Safebrowsing in SeaMonkey for recent changes in Firefox. Follow up bug of bug 920951 Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Old SeaMonkey API key does no longer work but the lists are downloaded. Ratty found out that Google throttles in this case.
  • bug 1210791 Get rid of XULPPFLAGS in ChatZilla. ChatZilla l10n xpi will be ok afterwards for c-r and up.

Working on:

  • bug 1258226 Remove debugQA from SeaMonkey. Input please if this should be up for reviewed if we should keep debugQA in it’s current state.
  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrian Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds. Will be a mood point if above bug is accepted.

Titbits:

  • c-r and up should build now out of the box. bug 1258206 is in as a successor for bug 1167346 comm-aurora builds are not building due to DOMi and ChatZilla pulling from revisions earlier…. It still needs to be checked into c-c so that the next merge won’t break it again.

Other things on my mind:

  • SeaMonkey needs reviewers. Ratty is not SuperRatty and can do it alone 🙂
  • –enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.
  • Alternate distribution path for SeaMonkey should be evaluated. It still builds and works fine but without builds in the hands of users doesn’t make much sense.
  • SeaMonkey compiles fine under VS2015 Update 2 RC with Windows 10 SDK. x86 builds produced here still works fine under Windows XP SP3. x64 build is stable for daily use in my eyes (same with VS2013).
  • m-c switched to VS2015 Update 1 and Windows 10 SDK on 03/25/2016!
  • bug 1244467 Localized Builds: ChatZilla language pack missing from SeaMonkey installer package will not be fixed by bug 1210791
  • Aero Peek is broken in c-b and up see bug 1256714. I didn’t find something which could have caused this. Got it back briefly yesterday in 2.45a1 so might be e10s related (something asynchronous timing out?).
  • When looking in Bugzilla what to do next I found a lot of in my eyes obsolete bugs in a short time. Who can close them. Tracking them in a meta bug?
Comment: I am working on this problem. We have lots of UNCONFIRMED Bugs, many of them old /obsolete. But in my systematic review (may be 3 … 5 each week) I find (approximately) 25% of these old bugs real bugs, half of them Core half of them really SeaMonkey bugs. With this speed review still will take 2 more years or so, but I think it’s better than a mass-close. — Rrbd (talk) 10:53, 29 March 2016 (PDT)

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Ratty

Fixed:

  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1255354 Create options to open the data manager and the addon manager in standalone windows instead of a browser tab.
  • bug 1255538 Fix trailing \whitespace and \tabs in tasksOverlay.js.
  • bug 1257348 GCLI close button disappears when hover [Devtools].
  • bug 1258161 XML parsing error in omni.ja!/chrome/toolkit/content/global/netError.xhtml [Toolkit].
  • bug 1254987 Fix comm-central fallout from |bug 1254410 Include app-specific configure files according to --enable-application/--enable-project|

Waiting for review:

  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • In Progress:
  • TODO:
  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1116223 Thunderbird: Move overrides to default theme chrome.manifest.

Other stuff:

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

rsx11m

Pushed to comm-central:

  • bug 851898 Zoom will not go past 300%, used to be able to zoom to +/-800%.
  • bug 1251874 Allow modification of minimum/maximum zoom levels in Content preference pane.
  • bug 1258295 Remove remnants of Security Policies preferences pane.
  • bug 1259422 Re-order entities in preferences.dtd to match Preferences dialog and remove unused strings.

Posted WIP patch:

  • bug 1259947 Investigate support of OneCRL in SeaMonkey.

Filed:

  • bug 1260315 Make modification of minimum/maximum zoom levels effective immediately in already opened windows.
  • bug 1256660 Donation link on “Development” page needs to point to the new “Donate” page.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • Got level-3 commit access now! bug 1257034.
  • End-user information and discussion on MozillaZine.

Any other business?

  • Daylight Saving Time in Northern America started on March 13; then Summer Time on March 27; winter time on 3 April in NZ and some parts of Australia; no clock change in East and South Asia; etc.
  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-03-29&oldid=1124716”

16-March-2016

SeaMonkey: 2016-03-15

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • Ewong for getting 2.40 out despite all odds and a broken hand.

Action Items

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

NEW

  • IanN to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
  • —

OPEN

  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Discussion:
    • Ewong has managed to get uploads to the S3 servers working – mostly.
    • Discussions have started with ewong, Callek, KaiRo, and others) about the route forward for both releases and infrastructure as well as growing the RelEng team and funding.
    • But the build team needs to be grown as ewong is not a superhero.
    • Council will have to decide if Adrian Kalla can be part of our RelEng team.
    • FRG: All trees are building locally just fine with client.py fixes for chatzilla and dom-inspector. Running 2.43 now.
  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until January at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.43a1 dated 9-Jan-2016 for L32 & L64, 6-Jan-2016 for Mac, and 2.42a1 dated 11-Nov-2015 for W32. No 2.44a1 yet, to parallel Firefox 47.0a1 which is being published every night (or every day depending on your timezone).
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [15th March 2016]
    • [comm-central, comm-aurora and comm-beta]
      • Busted due to a host of bugs. [:ewong : currently busy fixing the mess I made with the 2.40 updating to check.]
  • See RelEng page for the RelEng status history.

Release Train

  • Looks like ewong has managed to push 2.40 to the release servers at least for 2.40.

Discussion:

  • KaiRo: We should get a 2.42 release done based on Gecko 45 ESR and then only concentrate on getting nightly to build and run well and ignore everything in between for the moment. We can then do as many 2.42.x security updates based on ESR as we want before we get something out of nightly that is in good shape again.
  • Everyone agreed to skip 2.41.
  • Frg: Chatzilla locale generation still broken. Frg and Adrian to deal with this.

Carried forward from discussion at last meeting:

  • IanN suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta “release”. L10N Translations might be problematic however rsx11m says using ESR would be “safer” with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some “deal” to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that’s just simple patches such as label changes or adding a checkbox). rsx11m would go with {comm,mozilla}-esr45 and merge any “safe” patches from comm-beta but that may need some talking to l10n if string changes are involved.
  • Adriank thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 final (tracking bug 1233615) was partially released March 14, 2016
    • Updating failed due to PEBKAC. Currently rectifying this issue.
  • Merges were performed as scheduled on March 7:
    • comm-release default is now on SM 2.42.
    • comm-release and mozilla-release are now on 45.0.
    • comm-esr45 and mozilla-esr45 are now current.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings (outdated), altertative list started (currently Rainer Bielefeld is the only active maintainer)
  • Lightning betas are up for 2.40, 2.41, and 2.42.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (0)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1254987 (Fix comm-central fallout from |bug 1254410 - Include app-specific configure files according to --enable-application/--enable-project|). All comm-central applications are not building due to bug 1254410 jcranmer, glandium, et all are looking into this.
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, Will be fixed in SeaMonkey bug 1222816.
      • 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
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 10 new, 9 fixed, 13 triaged.

  • low-medium triaging effort, low number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! For relevant patches see previous meeting notes.
    • Unfortunately changes in DevTools keep bit-rotting my patch and it’s a P.I.T.A. to keep up.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The HowTo page has been moved to SeaMonkey/QA/Triage HowTo. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

Open reviews/flags:
68 review
5 super-review
3 ui-review
13 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

ewong

  • busy getting 2.40 to worry about other stuff.
    • with the busted updates… even more busy.

frg

Waiting for review:

  • bug 1055954 popup exceptions are not added. Please review and let me know if it’s ok. Contains string changes.
  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Contains string changes and hopefully will not miss the next cycle. I am done here and any changes will be need to put in new bugs.
  • bug 1251368 SeaMonkey cookie code needs to be updated to take into account mozilla-central bug 1245184. Might work whithout checking bug 1188348 in first but not tested. 2.44 and up affected.
  • bug 1250600 Update Safebrowsing in Seamonkey for recent changes in Firefox. Follow up bug of bug 920951 Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Old Seamonkey api key does no longer work but the lists are downloaded. Ratty found out that Google thottles in this case.

Working on:

  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.

Otherwise didn’t have much time in the last two weeks. Will see what I can do next.

Tidbits (didn’t see the mentiond bugs changed since the last time):

Chatzilla imho only needs one more patch and it should build l10n for 2.41 and up:

Would also need new tags for client.py as stated in:

  • bug 1167346 comm-aurora builds are not building due to DOMi and Chatzilla pulling from revisions earlier…

This might clear up:

  • bug 1244467 Localized Builds: Chatzilla language pack missing from Seamonkey installer package

Other things on my mind:

  • enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.
  • I absolutly hate the new Firefox build system. This seems to be based on cryptic on cryptic on cryptic scripts. Still prefer plain autoconf and configure.
  • Alternate distribution path for Seamonkey should be evaluated. It still builds and works fine but without builds in the hands of users doesn’t make much sense.
  • Seamonkey compiles fine under VS2015 Update 2 RC. x86 build still works fine under Windows XP SP 3 too. x64 build is stable for daily use (same with VS2013).
  • I think the council should replace it’s inactive members. Too much going on which needs attention.

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1252308 Update en-GB for Gecko 45
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Ratty

Fixed:

Needs review:

  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.

Waiting for review:

  • bug 1255354 Create options to open the data manager and the addon manager in standalone windows instead of a browser tab.
  • bug 1255538 Fix trailing \whitespace and \tabs in tasksOverlay.js.

Other stuff:

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

rsx11m

Landed on comm-aurora:

  • bug 1245110 Remove help about (now removed) “Ask for each cookie” option in preferences dialog.

Waiting for ui-review (necessary?):

  • bug 851898 Zoom will not go past 300%, used to be able to zoom to +/-800%.

Waiting for reviews:

  • bug 1251874 Allow modification of minimum/maximum zoom levels in Content preference pane.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • Daylight Saving Time in Northern America starts on March 13; then Summer Time on March 27; winter time on 3 April in NZ and some parts of Australia; no clock change in East and South Asia; etc.
  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-03-15&oldid=1122128”

2-March-2016

SeaMonkey: 2016-03-01

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Agenda

  • Who’s taking minutes? -> Ratty
  • 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

  • —

OPEN

  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek is winding down his involvement over the next 12 months. Possible replacement: Adrian Kalla (adriank).
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
      • The loaner machine was decommissioned without notice.
      • Got a new loaner.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.43a1 dated 9-Jan-2016 for L32 & L64, 6-Jan-2016 for Mac, and 2.42a1 dated 11-Nov-2015 for W32. No 2.44a1 yet, to parallel Firefox 47.0a1 which is being published every night (or every day depending on your timezone).
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [2nd February 2016]
    • [Tonymec] Building has stopped since 9 January. No tinderbox builds either. [frg] c-c would be clear to me. c-a pulls the wrong Chatzilla and Inspector again. Not sure if this is the cause. See bug 1167346. [IanN] ewong|away has mentioned looking at Jenkins.
  • See RelEng page for the RelEng status history.

Release Train

  • bug 1213721 is a tracking bug for migration from ftp.m.o to S3 for firefox and thunderbird. There’s a *scary* long list of dependent bugs over there.
    • How close were our staging scripts to Thunderbird’s prior to the S3 migration? They were relatively divergent, primarily because we don’t have signing infrastructure and Thunderbird’s infra uses MoCo firefox infra, and gets a lot of process for free. We should also consult Fallen to see how Thunderbird did the migration and what sort of issues cropped up.
    • Adrian Kalla is still producing his localized builds. Ratty suggests that we should put out a notice on the default SM start page to tell people where they can download the latest 2.4x release builds (Mozilla-release is currently at Firefox 45 which corresponds to SeaMonkey 2.42).
    • IanN suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta “release”. L10N Translations might be problematic however rsx11m says using ESR would be “safer” with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some “deal” to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that’s just simple patches such as label changes or adding a checkbox). rsx11m would go with {comm,mozilla}-esr45 and merge any “safe” patches from comm-beta but that may need some talking to l10n if string changes are involved.
    • Adriank thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 final (tracking bug 1233615) is in progress: in limbo.
    • 2.40 is currently mired in a swamp so deep it makes the Marianna Trenches look like a shallow pool.
      • Uploading is not the problem. It’s the problem of the following facts:
        • The S3 migration did away with our stage.mo site. (It is gone)
        • Our stage.mo site scripts depended entirely on stage.mo.
        • We need to redo our scripts to play ‘pass the bucket’ on the S3 server, which requires some S3 figuring out.
    • Without Callek, we are stuck.
    • build #4 are up for all platforms and locales
    • Build #5 was tagged February 16th, but no candidate builds yet
      • Build #5 was manually tagged. Not sure there’ll be a build 5.
    • Windows builds aren’t signed yet
    • apparently there is an issue with uploading those builds to the new S3 infrastructure [1] See bug 1223633 and bug 1213721
  • comm-release default moves from 2.41 to 2.42 after the merge.
  • Next merges scheduled for March 7 (February 29th: beta→release).
    • mozilla-release is now on 45.0.
    • both mozilla-esr45 and comm-esr45 are established.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings (outdated), altertative list started (currently Rainer Bielefeld is the only active maintainer)
  • Lightning betas are up for 2.40, 2.41, and 2.42.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [2].
    • 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 [3], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (0)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, Will be fixed in SeaMonkey bug 1222816.
      • 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
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [4]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 24 new, 3 fixed, 13 triaged.

  • low-medium triaging effort, average number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! For relevant patches see previous meeting notes.
    • Unfortunately changes in DevTools keep bit-rotting my patch and it’s a P.I.T.A. to keep up.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The HowTo page has been moved to SeaMonkey/QA/Triage HowTo. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

Open reviews/flags:
67 review
5 super-review
2 ui-review
13 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

frg

Waiting for review /feedback:

  • bug 1055954 popup exceptions are not added. Please review and let me know if it’s ok. Contains string changes and clock for next merge day is ticking…
  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Please review. Clock for next merge day is also ticking here…

Working on:

  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.
  • bug 1250600 Update Safebrowsing in Seamonkey for recent changes in Firefox. Follow up bug of bug 920951 Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Seamonkey misses and api key and maybe even a client id.

Otherwise just looking through the unassigned bug list and see what I might be able to fix.

Tidbits (didn’t see the mentiond bugs changed since the last time):

Chatzilla imho only needs one more patch and it should build l10n for 2.41 and up:

Would also need new tags for client.py as stated in:

  • bug 1167346 comm-aurora builds are not building due to DOMi and Chatzilla pulling from revisions earlier…

This might clear up:

  • bug 1244467 Localized Builds: Chatzilla language pack missing from Seamonkey installer package

Other things on my mind:

  • enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.
  • Firefox build system seems to change to a python based configure. Check m-c for old-configure.in. Works for now with Seamonkey but might break soon.
  • Alternate distribution path for Seamonkey should be evaluated. It still builds and works fine but without builds in the hands of users doesn’t make much sense.

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Rainer Bielefeld

All postponed to next meeting in favor of more important release and distribution issues:

currently working on
  • Bug reporting and confirmation as usual
  • Improving usability of dictionaries available for SeaMonkey (low priority)
ToDos / Pending

(Discussion required for all)

  • Donating and so on: Current situation very unsatisfying due to unresolved
    • bug 1165707 – Publish information concerning SeaMonkey e.V.
    • bug 1197554 – Balance sheet (statement of accounts) for donations should be published
    • bug 1191707 – Download: redirect users to detour via Donate / Contribute Request web page
I am planning alternative donation, decision today
  • Pogress bundling lomon_juice’s add-on AMO-Browsing-for-SeaMonkey
    • I already have some Ideas for smaller enhnacements. but as far as I know License statement still missing, so we can’t do anything with it. this problem blocks
      • bug 1230722 – Include “AMO Browsing for SeaMonkey”-add-on into SeaMonkey release bundle
      • bug 1224520 – Upload “AMO Browsing for SeaMonkey” to AMO
      • bug 1145026 – AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane
      • bug 1151227 – Add-on Manager discovery pane: add Banner with link to Add-on-converter
Any Ideas?
I want to discuss
Currently for some good reasons we have that guideline, but that, of course, requires that owners decide within acceptable time.

  • Example for the problem: bug 56418 – [SM] add folder column so bookmark search results shows where bookmark is in folder hierarchy
  • Suggestion: If a QA volunteer contributes plausible reasons that a bug deserves WONTFIX, he adds the Module Owner to CC and asks for decision: WONTFIX, Assign to someone or at least adds a possible Assignee to CC. For practicability reasons the QA volunteer will do an own decision if within 30 days there is no clear statement that SeaMonkey will do a fix (and be able to do a fix).
  • Basics: I saw “This page was last modified on 3 February 2013, at 05:42.” – that is not inspiring confidence. Can someone with competence drop some outdated contents?

Nevertheless I will launch an alternative donation method until end of this week

Ratty

Fixed:

  • bug 1224907 Bookmarks Manager Search box is missing in SeaMonkey 2.3.9.

Needs review:

  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1238428 Workaround the NS_APP_PROFILE_DEFAULTS_{NLOC_,}50_DIR directory keys removed in bug 1234012.

In Progress:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.

TODO:

  • Long list of bugs I want to fix but realistically speaking I don’t have the time to even look at things.

Other stuff:

  • Did some reviews and approvals.
    • Spent some time burning down my review queue. Not too successful.
    • Helped to onboard a new contributor or two.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.

rsx11m

Waiting for comm-aurora/beta approval:

  • bug 1245110 Remove help about (now removed) “Ask for each cookie” option in preferences dialog.

Waiting for reviews:

  • bug 851898 Zoom will not go past 300%, used to be able to zoom to +/-800%.

Spun off:

  • bug 1251874 Allow modification of minimum/maximum zoom levels in Content preference pane.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

tonymec

  • Not much this fortnight, QA business as usual.
  • I learnt that to fix a “good first bug” in Toolkit you must have either or both of the resources to compile your own Firefox, or “Level 1” push permissions (to push to Try). In the case at hand, mother-language-level knowledge of both XUL and -moz- extensions to CSS would have been a very serious plus. ;-/
    • (“Experience is what you get when you don’t get what you wanted.”)
  • To Rainer above, about the WONTFIX resolution:
    • I’d prefer to play by Mozilla rules even though it seems possible that we won’t be a Mozilla product much longer. At least it makes it easier to go back and forth between Seamonkey specific bugs and shared-code bugs.
    • It used to be that the official Mozilla policy was that only an owner or peer could set WONTFIX. (I can’t find back the page which said that.) The current MDN wording is that a developer decides that the bug can’t or won’t be fixed. At least owners ans peers are well-defined terms: see the SeaMonkey project areas page or the All Modules page. But who is or isn’t a “developer”? An owner, peer, or Council member probably is one; a “New to Bugzilla” person probably isn’t; but I don’t see a clear-cut boundary. One possible definition is «someone who habitually writes patches, and can even fix “non-good-first” bugs». Rainer seems to have a wider definition in mind.
    • Maybe different rules can be set for SeaMonkey. Since Neil is the official project owner, his opinion would carry quite some weight; though by past experience he seems to prefer playing King Log than King Stork.

Any other business?

  • Daylight Saving Time coming up (again…) on March 13; then Summer Time on March 27; winter time on 3 April in NZ and some parts of Australia; no clock change in East and South Asia; etc.
  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-03-01&oldid=1119449”

17-February-2016

SeaMonkey: 2016-02-16

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • Rainer Bielefeld for trying to get things organized

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

  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • [frg] Is there any hope that Mozilla fixes the build bots? if not an alternate distribution plan should be developed.
  • [IanN] I know there is working going on but Callek_cloud9 and ewong|away probably know more.
  • Ratty thinks we really should plan for a alternative distribution plan. Suggests Jenkins as an alternative to buildbot. Unfortunately he hasn’t been able to get a hold of ewong for the last week.
  • IanN will talk to our RelEng about this. We need some simple but effective and easy to maintain.
  • [frg] l10 seems to be generally broken or problematic. Seeing lots of commits in the Firefox Beta tree.
  • [rsx11m] no visible action on getting 2.40 out either
  • [Ratty] I may start uploading my private builds to callek.net. Will have to do some coordination with Adrian Kalla who is doing some L10n builds on Linux.
  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
      • The loaner machine was decommissioned without notice.
      • Got a new loaner.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.43a1 dated 9-Jan-2016 for L32 & L64, 6-Jan-2016 for Mac, and 2.42a1 dated 11-Nov-2015 for W32. No 2.44a1 yet, to parallel Firefox 47.0a1 which is being published every night (or every day depending on your timezone).
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [2nd February 2016]
    • [Tonymec] Building has stopped since 9 January. No tinderbox builds either. [frg] c-c would be clear to me. c-a pulls the wrong Chatzilla and Inspector again. Not sure if this is the cause. See bug 1167346. [IanN] ewong|away has mentioned looking at Jenkins.
  • [19th January 2016]
    • [comm-central]
  • [8th December 2015]
  • No Update. Ewong is hospitalized. Get well soon!
    • Excluding Windows, the tree is green for most part. We’re down one osx64 slave.
    • Re: Tests. Still broken.
      • Currently bug 1209378 is in progress to fix the perma-brokeness of our testing infrastructure; but it is ‘hard’.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 final (tracking bug 1233615) is in progress: in limbo.
    • Without ewong we are stuck.
    • IanN to check with Callek_cloud9 to see if he can help.
    • build #4 are up for all platforms and locales
    • Windows builds aren’t signed yet
    • apparently there is an issue with uploading those builds to the new S3 infrastructure [1] See bug 1223633 and bug 1213721
  • comm-release default tip is on 2.41 now.
  • Next merges scheduled for March 7 (February 29th: beta→release).
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Lightning betas are up for both 2.40 and 2.41.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [2].
    • 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 [3], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (0)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, Will be fixed in SeaMonkey bug 1222816.
      • 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
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [4]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 17 new, 3 fixed, 6 triaged.

  • low triaging effort, low number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! Relevant patches:
    • bug 1208112 Package DevTools client in SeaMonkey now that it’s been moved out of /browser/ [checked-in].
    • bug 1223338 Add DevTools client L10N language files to SeaMonkey builds [checked-in].
    • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
    • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
    • Not working yet: WebIDE and Responsive Design. But everything else seems to work.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The HowTo page has been moved to SeaMonkey/QA/Triage HowTo. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

Open reviews/flags:
66 review
6 super-review
1 ui-review
14 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

frg

Waiting for review:

  • bug 1055954 popup exceptions are not added. Please review and let me know if it’s ok. Contains string changes and clock for next merge day is ticking…
  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Please review. Clock for next merge day is also ticking here…
  • bug 1200263 Help → Report Web Forgery … does nothing.

Working on:

  • bug 1238767 Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.
  • bug 920951 Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central: Got it working with an external api key and added a second alternate patch to the bug. Might still needs some work but it blocked and seems to work generally. I can now turn it off again:) Checking downloads would need the new Download Manager imho. Tracking protection might be next on the platter.

Otherwise just looking thru the unassigned bug list and see what I might be able to fix.

Tidbits:

Chatzilla imho only needs one more patch and it should build l10n for 2.41 and up:

Would also need new tags for client.py as stated in:

  • bug 1167346 comm-aurora builds are not building due to DOMi and Chatzilla pulling from revisions earlier…

This might clear up:

  • bug 1244467 Localized Builds: Chatzilla language pack missing from Seamonkey installer package

Other things on my mind:

  • enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.

Rainer Bielefeld

currently working on
 
ToDo / Pending

  • From SeaMonkey/StatusMeetings/2016-02-02#Rainer_Bielefeld:
    • No success with AMO upload of lomon_juice’s add-on-browser because of license issues
    • After general fix for bug 1153577 – Users should be able to hide the menubar and show it with the ALT key some non-WIN-OS related issues, what might become annoying when we get 2.40 builds
  • See I want to discuss!
 
I want to discuss
  • How to track Core bugfixes for SeaMonkey
Problem: I don’t know what bugfixes when will be introduced into SeaMonkey (manually? automatically?). For example bug 1193153 – Copy/paste from a plain text editor has been fixed for TB45 2015-12-01, but I still see it in SM 2.44a1. Forgotten?
Possible method of resolution:

  • Adventage: compared to any manually maintained lists: Allows bugzilla Queries
  • Disadventages:
currently some private solution, nowhere defined tags
QA-Whiteboard field not available for all components where required
Uncommon spelling “seamonkey-2.42” with hyphen
  • Alternative: Leave SM Bugs open for tracking
  • Adventage: easy tracking in BZ
  • Disadventages:
We do not always have SeaMonkey DUPs, should we really open such reports only for tracking?
This method with parallel Bugs is confusing, People might feel invited to leave comments …
Ideas: ?

Ratty

Fixed:

In Progress:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1238428 Workaround the NS_APP_PROFILE_DEFAULTS_{NLOC_,}50_DIR directory keys removed in bug 1234012.

On Hold:

  • bug 1239707 Switch to use in-tree version of compare-locales (SeaMonkey Part).

Needs Investigating:

TODO:

  • Fix Thunderbird defaut theme overrides.
  • Front end changes needed for bug 1042699 Block cross-origin add-on install requests.
  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1224907 Bookmarks Manager Search box is missing in SeaMonkey 2.3.9.
  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.

Other stuff:

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

rsx11m

Landed on comm-central:

  • bug 1245110 Remove help about (now removed) “Ask for each cookie” option in preferences dialog.

Waiting for comm-aurora/beta approval:

  • bug 1245110 Remove help about (now removed) “Ask for each cookie” option in preferences dialog.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

tonymec

I’m intentionally listing here what regards anything included in SeaMonkey, even shared components such as the Toolkit product or built-in extensions such as ChatZilla.

Any other business?

  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-02-16&oldid=1117293”

3-February-2016

SeaMonkey: 2016-02-02

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • No nominees this time

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

  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
      • The loaner machine was decommissioned without notice.
      • Got a new loaner.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Even en-US builds have stopped again. The latest trunk nightlies were 2.43a1 dated 9-Jan-2016 for L32 & L64, 6-Jan-2016 for Mac, and 2.42a1 dated 11-Nov-2015 for W32. No 2.44a1 yet, to parallel Firefox 47.0a1 which is being published every night (or every day depending on your timezone).
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [2nd February 2016]
    • [Tonymec] Building has stopped since 9 January. No tinderbox builds either. [frg] c-c would be clear to me. c-a pulls the wrong Chatzilla and Inspector again. Not sure if this is the cause. See bug 1167346. [IanN] ewong|away has mentioned looking at Jenkins.
  • [19th January 2016]
    • [comm-central]
  • [8th December 2015]
  • No Update. Ewong is hospitalized. Get well soon!
  • Excluding Windows, the tree is green for most part. We’re down one osx64 slave.
  • Re: Tests. Still broken.
    • Currently bug 1209378 is in progress to fix the perma-brokeness of our testing infrastructure; but it is ‘hard’.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 final (tracking bug 1233615) is in progress:
    • en-US build #4 are up for all platforms
    • localized builds are up for Linux and Mac OSX
    • new Windows loaner having issues with l10n builds
  • Merges were performed January 25th as scheduled.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Lightning betas are up for both 2.40 and 2.41.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (6)
targeted (0)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1243760 Replace nsPIDOMWindow with nsPIDOMWindowInner/Outer in comm-central due to bug 1241764.
    • bug 1244758 Rename nsAutoTArray to AutoTArray in Mailnews due to bug 1235261 (bustage fix).
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, bug 1125636
      • Toolkit meta bug for about:* pages: bug 1097111 – SeaMonkey tracking in bug 1133743
      • Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
      • Fallout thus far: bug 1133582 about:config (Modern)
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

Feature List, Planning

Bug statistics for the last two (full) weeks: 20 new, 7 fixed, 12 triaged.

  • low-medium triaging effort, low number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! Relevant patches:
    • bug 1208112 Package DevTools client in SeaMonkey now that it’s been moved out of /browser/ [checked-in].
    • bug 1223338 Add DevTools client L10N language files to SeaMonkey builds [checked-in].
    • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
    • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
    • Not working yet: WebIDE and Responsive Design. But everything else seems to work.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
    • The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The HowTo page has been moved to SeaMonkey/QA/Triage HowTo. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

Open reviews/flags:
64 review
6 super-review
1 ui-review
12 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

frg

Waiting for review:

  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. New version 6 patch just built.
  • bug 1200263 Help → Report Web Forgery … does nothing.
  • bug 1240284 Linker Warnings LNK4222 and LNK4017 when building Suite. Still need to build the upstream sdk patch.

Working on:

  • bug 1055954 popup exceptions are not added. I first thought about closing it as a duplicate of the Data Manager bug but the menu in Navigator is just bad. Will change it so that it resembles the cookie and image menu and not transfer control to Data Manager. WIP patch still needs some work but looks fine.

Tidbits:

Chatzilla seems to have a bad day lately. I still need private patches for 2 bugs to build l10n 2.41 and up:

  • bug 1240304 Old maximum version numbers in Chatzilla rdf files
  • bug 1210791 Get rid of XULPPFLAGS in Chatzilla

And the official builds miss the language pack:

  • bug 1244467 Localized Builds: Chatzilla language pack missing from Seamonkey installer package

And comm-aurora picks the wrong Chatzilla branch again. Didn’t file a bug yet.

On the backburner. Didn’t have much time to check

Other things on my mind:

  • enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1243064 Update en-GB for Gecko 44
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Rainer Bielefeld

currently working on
ToDo (postponed from meeting 2016-01-19
  • Improve Mentoring for new developer volunteers
I get requests of interested (but inexperienced) developers to help, but I hesitate to encourage them because most new developers will need intensive help for 5 (or so) first bugs until they become able to work independently. Unfortunatley we do not have proved and well known infrastructure for that like Newbies discussion forum (where they can help each other) and similar. So we lost Batchu Venkat Vishal, Tom Zhang, ytrackm-sannysm@yahoo.com (never started activity) and others. Any Ideas how to interest possible new developers in continuous and persevering contiibution to SeaMonkey?
  • Donating and so on: Current situation very unsatisfying due to unresolved
    • bug 1165707 – Publish information concerning SeaMonkey e.V.
    • bug 1197554 – Balance sheet (statement of accounts) for donations should be published
    • bug 1191707 – Download: redirect users to detour via Donate / Contribute Request web page
this should be discussed on IRC, I hope I will be able to participate
Other discussion items
  • Progress bundling lomon_juice’s add-on-browser? I think that is really important!
  • After general fix for bug 1153577 – Users should be able to hide the menubar and show it with the ALT key some non-WIN-OS related issues, what might become annoying when we get 2.40 builds

Ratty

Fixed:

  • Naught.

Working on comm-central bustage fixes:

In Progress:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1238428 Workaround the NS_APP_PROFILE_DEFAULTS_{NLOC_,}50_DIR directory keys removed in bug 1234012.
  • bug 1239707 Switch to use in-tree version of compare-locales (SeaMonkey Part).

TODO:

  • Fix Thunderbird defaut theme overrides.
  • Front end changes needed for bug 1042699 Block cross-origin add-on install requests.
  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1224907 Bookmarks Manager Search box is missing in SeaMonkey 2.3.9.
  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.

Needs Investigating:

Other stuff:

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

rsx11m

Landed on comm-central and comm-aurora:

Filed for for 2.42.x if continued on 45 ESR:

  • bug 1240738 Bugs with l10n changes that need uplifting to 2.42.x in case we build from 45.x ESR repositories. (meta)
    • ref. bug 1229270 Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • Closed remaining 2.35 and 2.38 tracking bugs along with pending but obsolete post-landing review requests.
  • End-user information and discussion on MozillaZine.

tonymec

Any other business?

Donations to SeaMonkey:

  • [Rainer_Bielefeld]If there still is a little time remaining: I have a question concerning SeaMonkey donation status. Do we get money? if yes, how much? used for what? Currently all that is not very transparent.
  • [Ratty]The eV gets the money.
  • [frg]Second that. Would like to donate again but not sure where the money goes hoch much and what they do with it. Intransparent unfortunately
  • [Ratty]mcsmurf did promise to provide an accounting. Rainer_Bielefeld: maybe you can remind him?
  • [Rainer_Bielefeld]I know. but: bug 1165707 Publish information concerning SeaMonkey e.V. ? It looks as if that ev does not really exist :-/
  • [Ratty]You two live in Germany. Could try holding mcsmurf’s feet over a fire?
  • [IanN]I will remind mcsmurf on that
  • [tonymec]das Gelt geht zur eV, aber wo geht es daraus hin?
  • [Rainer_Bielefeld]I think we need some public relations: Thanks to donators, …
    • Yes, I will contact mcsmurf.
  • [frg]Yes. To do the job is great but to promote it is neccessary or we will go down anyway.
  • [Rainer_Bielefeld]And publish results in the blog
    • Anything new concerning Progress bundling lomon_juice’s add-on-browser? I think that is really important, ofr me that add-on is great help
  • [frg]Rainer_Bielefeld: If the others think I am already on par for simple thingsa I can help other developers.
  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-02-02&oldid=1115429”

20-January-2016

SeaMonkey: 2016-01-19

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Agenda

  • Who’s taking minutes? -> Ratty
  • 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

  • —

OPEN

  • Need to port Sync 1.5 to SeaMonkey – IanN has spoken briefly to ewong about options, Ratty might be able to help too.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
      • The loaner machine was decommissioned without notice.
      • Got a new loaner.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Buildmaster is up and running, and produces en-US builds, see 9/16 meeting’s Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [19th January 2016]
    • [comm-central]
  • [8th December 2015]
  • No Update. Ewong is hospitalized. Get well soon!
  • Excluding Windows, the tree is green for most part. We’re down one osx64 slave.
  • Re: Tests. Still broken.
    • Currently bug 1209378 is in progress to fix the perma-brokeness of our testing infrastructure; but it is ‘hard’.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 beta has been cancelled.
  • SeaMonkey 2.40 final (tracking bug 1233615) has been tagged January 14th but no candidate builds.
    • [frg] wants to know if we should we skip 2.40 and go straight to 2.41 which just arrived in mozilla-release yesterday. Using private builds for 4 weeks. No problems in daily browsing.
    • [IanN] It will depend on what happens with comm-central/aurora/beta and Thunderbird; but we may end up on a very different release schedule in the end.
    • IanN wants to talk to the releng team about the release schedule generally.
  • Next merge is scheduled for January 25th (in less than a week from now).
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Lightning button icons are not shown on the mail-toolbox making them invisible. Fixed in bug 1223898 CSS chould be simplified though (bug 1236982).
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

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

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, bug 1125636
      • Toolkit meta bug for about:* pages: bug 1097111 – SeaMonkey tracking in bug 1133743
      • Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
      • Fallout thus far: bug 1133582 about:config (Modern)
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.

Feature List, Planning

Bug statistics for the last two (full) weeks: 28 new, 4 fixed, 5 triaged.

  • low triaging effort, average number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! Relevant patches:
    • bug 1208112 Package DevTools client in SeaMonkey now that it’s been moved out of /browser/ [checked-in].
    • bug 1223338 Add DevTools client L10N language files to SeaMonkey builds [checked-in].
    • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
    • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
    • Not working yet: WebIDE and Responsive Design. But everything else seems to work.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The HowTo page has been moved to SeaMonkey/QA/Triage HowTo. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

Open reviews/flags:
65 review
5 super-review
1 ui-review
14 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

frg

Waiting for review:

  • bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords.
  • bug 1200263 Help → Report Web Forgery … does nothing.
  • bug 1240304 Old maximum version numbers in Chatzilla rdf files

Tidbits:

  • Fixes already in bug 1210791 – Get rid of XULPPFLAGS in Chatzilla and bug 1240304 allowed me to build a fully working localized de Chatzilla bundled with the Seamonkey installer.
  • I think that localized c-c builds are broken and filed bug 1238767 Localized Suite build fails in DebugQA
  • Think I found a good workaround for an old annoying problem for bug 521861 After creating news account through clicking news URL Account Wizard is broken. Would appreciate some feedback if the patch there should be made reviewable
  • The Data Manager bug 1188348 should be reviewed soon for a possible inclusion in ESR 45. It contains string changes. This is currently so broken it bugs alot of people. Usually at least one comment each week. If the patch is not ok I am willing to do additional changes as fast as time and knowledge permits but I am unwilling to put the new password permissions page back into the permissions page because of, which I think, would result in spaghetti code.

Other things on my mind:

  • With backported bugs bug 1198936 bug 1204752 and bug 1229604 Seamonkey 2.40 x86 and x64 and up compiles and works 100% fine using VS2015 Update 1. So if Mozilla decides to use it in the future for Firefox we do have nothing to fear (other than another build bot upgrade). Tested the x86 build under XP SP3 and Server 2003 x64 and use 2.41 x64 daily.
  • enable-optimize=-O2 should be used for Windows release builds. Linux gcc –enable-optimize optimizes for speed. With VS2013 it optimizes for size. Resulting O2 Windows build feels a lot snappier.

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Rainer Bielefeld

currently working on
ToDo
  • Improve Mentoring for new developer volunteers
  • Donating and so on: Current situation very unsatisfying due to unresolved
    • bug 1165707 – Publish information concerning SeaMonkey e.V.
    • bug 1197554 – Balance sheet (statement of accounts) for donations should be published
    • bug 1191707 – Download: redirect users to detour via Donate / Contribute Request web page

Ratty

Fixed:

  • bug 1233997 about:debugging should be available to all applications that ship the Devtools client (and not just Firefox) [Devtools]

In Progress:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • bug 1235805 Rollup patch: Add preload content policy types for images (bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.
  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1236982 Simplify SeaMonkey CSS for Lightning toolbar buttons.
  • bug 1238428 Workaround the NS_APP_PROFILE_DEFAULTS_{NLOC_,}50_DIR directory keys removed in bug 1234012.
  • bug 1239707 Switch to use in-tree version of compare-locales (SeaMonkey Part).

Needs Investigating:

  • bug 1240304 Old maximum version numbers in Chatzilla rdf files.

Need to look into this:

TODO:

  • Fix Thunderbird defaut theme overrides.
  • Front end changes needed for bug 1042699 Block cross-origin add-on install requests.
  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1224907 Bookmarks Manager Search box is missing in SeaMonkey 2.3.9.

Other stuff:

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

rsx11m

Landed on comm-central and comm-aurora:

  • bug 1238266 Move hidefor attribute from IDLE checkbox to surrounding vbox.
  • bug 1238374 Access key conflict for new IDLE checkbox in IMAP Server Settings.

Landed on comm-central, possible candidate for 2.42.x if continued on 45 ESR:

  • bug 1229270 Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.

Waiting for checkin:

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

tonymec

  • FIXED
    • bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs
    • bug 1235199 Remove “Ask for each cookie” radiobutton in preferences dialog now that its backend is gone r=Neil a-a,a-b=Ratty 2.40-unaffected.
  • QA (bugs moved, resolved as INVALID, DUPLICATE, etc): business as usual.

Any other business?

  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-01-19&oldid=1113230”

6-January-2016

SeaMonkey: 2016-01-05

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

SeaMonkey Meeting Details

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • I propose Frank-Rainer Grahl who’s been doing a lot of testing and bug reporting on Windows recently, mostly on own-compiled W64 builds; also some bug fixing. Any seconds? — Tonymec (talk) 10:32, 26 December 2015 (PST)
    • Seconded by Ratty and IanN

Action Items

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

NEW

  • —

OPEN

  • Need to port Sync 1.5 to SeaMonkey – IanN has spoken briefly to ewong about options, Ratty might be able to help too.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.
    • [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don’t have to worry about the python stuff.

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Buildmaster is up and running, and produces en-US builds, see 9/16 meeting’s Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [8th December 2015]
  • No Update. Ewong is hospitalized. Get well soon!
  • Excluding Windows, the tree is green for most part. We’re down one osx64 slave.
  • Re: Tests. Still broken.
    • Currently bug 1209378 is in progress to fix the perma-brokeness of our testing infrastructure; but it is ‘hard’.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 beta has been cancelled.
  • SeaMonkey 2.40 final released/scheduled ???
  • Last merge was December 14th as scheduled.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Lightning button icons are not shown on the mail-toolbox making them invisible. Fixed in bug 1223898 but we should consider moving the CSS from suite to Lighting.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.40

open tracking (0)
tracking requests (3)
targeted (0)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, bug 1125636
      • Toolkit meta bug for about:* pages: bug 1097111 – SeaMonkey tracking in bug 1133743
      • Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
      • Fallout thus far: bug 1133582 about:config (Modern)
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.

Feature List, Planning

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

  • good triaging effort, average number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! Relevant patches:
    • bug 1208112 Package DevTools client in SeaMonkey now that it’s been moved out of /browser/ [checked-in].
    • bug 1223338 Add DevTools client L10N language files to SeaMonkey builds [checked-in].
    • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
    • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
    • Not working yet: WebIDE and Responsive Design. But everything else seems to work.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.

Open reviews/flags:
??? review
??? super-review
??? ui-review
??? feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

— Discussion on locale translations for DOMi and Chatzilla —

  • [frg] Localized Chatzilla builds currently break suite compile starting with 2.41. See bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • [IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?
  • [frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.
  • [IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.
  • [IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB’s new merged (c-c + m-c) repository?
  • [Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don’t know how this will work.
  • [IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1230855 Update en-GB for Gecko 43
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Neil

Checked in to comm-central, might need uplift:

Checked in to comm-central, comm-aurora and comm-beta:

  • bug 1222491 Update Modern theme for recent changes in web notifications.

Checked in to comm-beta:

Still waiting for feedback:

  • bug 888915 Convert SeaMonkey Downloads Manager to Downloads.jsm

Still waiting for review:

Ratty

Fixed:

  • bug 1211166 Use AppConstants in SessionRecorder.jsm [Toolkit]
  • bug 1226048 “Save View as Folder” and “File->New->Saved Search”: missing folder [comm-release]
  • bug 1227305 ReferenceError: can’t access lexical declaration `max’ before initialization causes “DOM Inspector” to stop working [DOM Inspector]
  • bug 1229803 Port bug 1228444 (Rename DIST_FILES to FINAL_TARGET_PP_FILES) to DOM Inspector.
  • bug 1231984 Add-on SDK tabs problem: domWindow.gBrowserInit is undefined.
  • bug 1233063 ProfileManager UI broken. Copied the strings removed in bug 1232629 to /suite/.
  • bug 1233433 [Installer] Consolidate Push client interfaces – SeaMonkey part.
  • bug 1233509 Update packaging for Push client interfaces (bug 1189998) Thunderbird/Instantbird parts.
  • bug 1233524 The Create Profile Wizard says “Click Done …” when the button is called “Finish” and “Click Finish …” when the button is called “Done” [Toolkit::Profiles]

Waiting for review:

  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.
  • bug 1235805 Rollup patch: Add preload content policy types for images (Bug 1048048) Use the loading document’s principal to populate loadInfo for Favicons instead of using systemPrincipal (Bug 1119386) nsITaskbarPreview::Invalidate no longer throws when not visible.

In Progress:

  • bug 1222816 Restore about:config UI (Config Editor) to old appearance by overriding Toolkit’s Project Chameleon styles.
  • bug 1229810 Port bug 1228444 and bug 1228467 to Chatzilla.
  • bug 1233997 about:debugging should be available to all applications that ship the Devtools client (and not just Firefox) [Devtools]

TODO:

  • Fix Thunderbird defaut theme overrides.
  • Front end changes needed for bug 1042699 Block cross-origin add-on install requests.
  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1224907 Bookmarks Manager Search box is missing in SeaMonkey 2.3.9.

Other stuff:

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

rsx11m

Waiting for checkin on comm-central:

  • bug 1229270 Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • —
Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-01-05&oldid=1111482”

9-December-2015

SeaMonkey: 2015-12-08

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

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

  • —

OPEN

  • Need to port Sync 1.5 to SeaMonkey – IanN has spoken briefly to ewong about options, Ratty might be able to help too.
  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
    • Unfortunately nobody knows exactly how addons.mozilla.works because there’s no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.
    • About specific aspects of this problem, see: bug 1230796, bug 1230804, bug 1230806 and maybe more.

CLOSED

  • Send a delicious cake to each of our RelEng Team for all their hard work getting SeaMonkey 2.35 and 2.38 out of the door. Assigned to Ratty.
    • Ewong and Callek have received theirs.
  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Callek: Regarding the windows systems, sadly no progress yet. I’m hopeful we can get done sooner than later, I’m realistic expecting it won’t be until january at earliest.
    • Ewong will set up a cron job to do semi regular builds on the loaner machine.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Buildmaster is up and running, and produces en-US builds, see 9/16 meeting’s Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [8th December 2015]
  • No Update. Ewong is hospitalized. Get well soon!
  • Re: Tests. Still broken.
    • Currently bug 1209378 is in progress to fix the perma-brokeness of our testing infrastructure; but it is ‘hard’.
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.39 was released November 8th, 2015.
  • SeaMonkey 2.40 beta out soonish is indefinitely delayed. Ewong is in a hospital and Callek is travelling.
    • (bug 1230393), however it won’t be earlier than 10th since there were a handful of changes that could affect our release process, the most notable of which was the “productdelivery move” (e.g. where we host our bits bug 1223633). We will need to do all the stuff manually.
  • Next merge scheduled for December 14th.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Lightning 4.4b2 shows no button icons (that’s for SeaMonkey 2.39). To be fixed in bug 1211643. The patch now has reviews. Ratty will check the patch in RSN to com-central, comm-aurora, and comm-beta. comm-release pending approvals.
  • We are looking for a new place to host the 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 this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    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.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • 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 [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on seamonkey-projects.org to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
    • The AMO Browsing for SeaMonkey extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a “built-in extension” besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane; the extension actually does much more than the bug’s Summary implies: for instance it gets rid of the stupid “You need Firefox 10 or later” popups.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Ratty has the Firefox Devtools up and running. We can now use the Firefox Devtools debugger in both remote and local mode.
    • Venkman is now totally retired R.I.P..

2.x (Last, Current, Next)

2.39

open tracking (0)
tracking requests (6)
targeted (2)
fixed (15)

2.Next

  • We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
    • bug 1003434 Add support for about:sync-progress.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 1209875 did break any builds of 2.41+ containing a localized ChatZilla – bug 1213641 filled
    • No en-US trunk builds later than 30 November yet (or even 11 November on win32). Aurora is currently building on Linux (L32 / L64) only.
  • Mozilla-central bugs that affect us:
    • Changes to Safe Browsing.
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, bug 1125636
      • Toolkit meta bug for about:* pages: bug 1097111 – SeaMonkey tracking in bug 1133743
      • Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
      • Fallout thus far: bug 1133582 about:config (Modern)
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.
      • mozilla-central bug 1189918 and bug 1190465 allow to fork Toolkit style pages for the classic/default/modern theme without harming theme developers. SeaMonkey bug 1022354 will move theme overrides to the theme manifests.
        • affected pages that should be reverted are about:config [bug 1222816], about:addons [bug 1222817], about:support [bug 1222818] (look ok in Modern but hurt in the Default theme).
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [3]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.

Feature List, Planning

Bug statistics for the last two (full) weeks: 27 new, 5 fixed, 15 triaged.

  • low triaging effort, average number of new bugs filed.
  • Ratty has a SeaMonkey build with a working Firefox Devtools!!!! Relevant patches:
    • bug 1208112 Package DevTools client in SeaMonkey now that it’s been moved out of /browser/ [checked-in].
    • bug 1223338 Add DevTools client L10N language files to SeaMonkey builds [checked-in].
    • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI. Waiting for review.
    • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey [Devtools]. Waiting for review.
    • Not working yet: WebIDE and Responsive Design. But everything else seems to work.
  • Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • Fundamental core features Firefox/Mozilla plans to remove:
    • bug 1222546 Product plan: remove support for heavyweight themes
      • if effective for all Toolkit applications, would render most 3rd-party themes disfunct
      • no sufficiently plausible specifics provided ‘why’ full themes ‘must’ no longer be supported
      • may prohibit Modern theme being shipped with or installed in SeaMonkey
      • removal is “decided” without any clear alternative envisioned
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.

Open reviews/flags:
61 review
5 super-review
2 ui-review
13 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as “official” ?

On October 7 two people asked in #seamonkey at a few minutes’ interval when there would be “official” 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the “Other languages” release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not “official”.

So — how are we going to get out of the following vicious circle? 64-bit builds are not “official” because too few users, and users don’t install them (some even prefer compiling their own) because they aren’t “official”.

Maybe change the online documentation? (perhaps as part of bug 1208822 “System Requirements page needs update”?)

— Tonymec (talk) 13:56, 7 October 2015 (PDT)

  • [ewong:] what’s the prerequisites of making the Linux64 builds ‘official’ aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. bug 1209378

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

IanN

  • Usual localising, testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Pending checkin for dependent bugs:
    • bug 653386 Consider overriding netErrorApp.dtd rather than netError.dtd
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1230855 Update en-GB for Gecko 43
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Neil

Checked in to comm-beta:

Still needs checkin:

  • bug 1222491 Update Modern theme for recent changes in web notifications.
  • bug 1223135 Switch Page Info to use principals.

Still waiting for feedback:

  • bug 888915 Convert SeaMonkey Downloads Manager to Downloads.jsm

Still waiting for review:

Ratty

Fixed:

  • bug 1022354 SeaMonkey forces 3rd-party themes to not use defaultFavicon.png but hardcode a bookmarks-item.png.
  • bug 1223344 Some tweaks to gDevTools.jsm to get Devtools working in SeaMonkey.
  • bug 1229495 Silence complaints about missing preprocessor directives in search plugins.
  • bug 1229876 Port bug 1229241 Differentiate preprocessed and non-preprocessed JS pref files (JS_PREFERENCE_FILES to JS_PREFERENCE_PP_FILES) [comm-central)
  • Parts of bug 1229419 (Port bug 1228444 to comm-central)
    • Rename DIST_FILES to FINAL_TARGET_PP_FILES. Supplemental Thunderbird patch.
    • Rename DIST_FILES to FINAL_TARGET_PP_FILES. Supplemental Instantbird patch.
  • bug 1230960 Remove some duplication in the buildconfig for the Thunderbird Default Theme

Waiting for review:

  • bug 1211166 Use AppConstants in SessionRecorder.jsm [Toolkit]
  • bug 1223341 Add the Firefox Devtools to the SeaMonkey UI.

In Progress:

TODO:

  • Fix Thunderbird defaut theme overrides.
  • Front end changes needed for bug 1042699 Block cross-origin add-on install requests.
  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • Port bug 1048048 add preload content policy types for images.
  • bug 1174466 Popup blocker: Need to allow popups opened by loaded javascript: URIs from the location bar. Regression from bug 896947.
  • bug 1224907 Bookmarks Manager Search Button is missing in SeaMonkey 2.3.9.

Other stuff:

  • Did some reviews and approvals.
    • Triaged some GFB review requests.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.

rsx11m

Landed on comm-central:

  • bug 1152644 Add UI in Notifications preference pane whether or not to use libnotify for new-mail alerts on Linux.

Waiting for reviews:

  • bug 1229270 Provide UI in Send Format pane for new mailnews.sendformat.auto_downgrade preference.

May need retargeting:

  • bug 1123673 Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites.

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • There will be no December 22nd meeting due to the holidays
    • next meeting January 5th, at the regular 13:00 UTC time again
  • —

SeaMonkey Meeting Details

Retrieved from “https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2015-12-08&oldid=1108722”

Older Posts »

Powered by WordPress