SeaMonkey/StatusMeetings/2015-12-08

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 8 December, 2015, 12:30 UTC
  • (7:30am Eastern, 12:30pm UK, 1:30pm Central Europe, 8:30pm Hong Kong)
  • TIME CHANGE! (only for this meeting)
• Location: #seamonkey IRC channel
• Further Read: Basics

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 has received his!
• —

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 chron 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.
• [24th November 2015]
  • All trees:
    • Windows platform still busted due to needing Win2008R2 installed.
    • We have a loaner which ewong is working on (see blog for more information).
    • L10n repacks are broken on aurora and central because the patch from bug 1210791 hasn't been reviewed yet.
  • comm-central:
    • Linux*: Green
      • (patches from bug 1187222 were post-land-review pushed.)
    • OSX64: Current status is that it is 'busted'; but this is only because of the backlog. (87 pending build jobs)
      • Possibly busted due to bug 1223633, but will need to get past the busted compile step.
  • comm-aurora:
    • Mostly green.
    • OSX64 is very backlogged; But busted because of bug 1223633. Even if not busted, it'd be orange in some parts but that's due to the firefox.dmg issue bug 958812.
  • comm-beta & comm-release:
    • OSX64: Red: due to bug 1223633
      • OSX64 - debug build : Orange: due to bug 958812

• 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 (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)

• Mozilla wants to separate Firefox and Thunderbird, in infrastructure and organizationally, which will likely affect SeaMonkey as well
  • discussions in mozilla.governance, mozilla.dev.apps.seamonkey, tb-planning, blog.lizardwrangler.com
  • unclear at this time what "separating the infrastructure" means
  • likely goes hand-in-hand with planned reduction of key features and future deprecation of the Gecko rendering engine
• SeaMonkey Statistics can be viewed at https://dataviz.mozilla.org Across all channels we have an approximate ADU of 120k.
  • Ratty suggests embedding these graphs somewhere on seamonkey-projects.org or https://dev.seamonkey.at
  • bug 1133728 Look at embedding dataviz information into the SeaMonkey website.
  • Links are broken again. Dataviz views now needs a SSO login. We need to find out how to expose a limited view for public consumption bug 1173006.
• See Basics page for the usual reminders.

2.39

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

• SeaMonkey 2.39 Release Notes

2.Next

• We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: 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: 22 new, 3 fixed, 14 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.
• 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
• 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. If no one objects, bug 1092632 will be RESOLVED FIXED after the New Year holidays.

Open reviews/flags: 54 review 5 super-review 1 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).

rsx11m

Waiting for checkin:

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

Working on:

• bug 1229270 Provide UI 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
• —