SeaMonkey/StatusMeetings/2016-05-24

From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details

Agenda

  • Who's taking minutes? -> frg
  • Nominees for Friends of the Fish Tank:
    • frg for doing a bunch of bustage fixes lately

Action Items

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

NEW

  • [Ratty:] rkent has stated that he will not uplift the suite parts of changesets to SeaMonkey branches that are perma-CLOSED unless he gets a perma-APPROVED from SeaMonkey team. Since he is the TB module owner and a TB-driver I think it's a reasonable request. approved by meeting participants
  • Google just announced V4 of the safebrowsing api. No actions currently needed.
  • —

OPEN

  • Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
    • Per bug 903439#c10, ewong has a Google API key (stating that for Geolocation service). Safe Browsing key is apparently still missing.
  • 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

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 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' has approved a patch which will update the builders to vs2015U2 so maybe there can be some progress seen soon.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • en-US trunk hourlies and nightlies are being published again since 2016-04-25 for L32, L64 and Mac but not Windows. Still no new langpacks or localized builds at ftp.m.o.
    • 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.
  • [24th May 2016]
    • [comm-central]
      • OSX64: busted due to bug 1260362. Yasm 1.2 needs to be installed.
      • Linux64 Nightly: busted due to bug 1275215
      • All trees: Location bar and Back/Forwad buttons broken because of bug 1272401. Patch is being reviewed now.
    • [comm-aurora]
      • OSX64: busted due to bug 1260362.
      • OSX64 Nightly: intermittent bustage due to not being able to access the crash stats token.
      • Linux64 build: busted due to bug 1275218
    • [comm-beta]
    • [comm-release]
  • See RelEng page for the RelEng status history.

Fixed Stuff Since Last Meeting

  • Linux (32&64) Trunk builds are still appearing at ftp.m.o., though some days the nightly is missing and only hourlies ("tinderbox-builds") are to be found.
  • Trunk is now built with Lightning packaged-in, as an unzipped extension in INSTALLDIR/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/ where INSTALLDIR may be (in a typical Linux case) /usr/local/seamonkey. See bug 516026 (Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled).

Release Train

  • Next release will be 2.43 (no ETA yet). Because 2.44 is coming up fast frg will ask ewong if he is able to get out a 2.43 soon. Otherwise 2.43 might be skipped also.
  • bug 1234012 will be backed out in a special m-r release branch for Seamonkey 2.43. This seems to cause major problems for Enterprise users in Firefox and may be backed out there too.
  • bug 1231349 will cause problems building l10n versions. Currently only a workaround exists.
  • Backup plan in case we need it is to do some releases off comm-esr45. These would be 2.42.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break Seamonkey.
  • Patches which do not concern Thunderbird could be be checked into comm-esr45 after getting approval too.
  • Next mozilla-beta→release migration is scheduled for May 30th, remaining merges for June 6th
  • Main action of comm-beta is in THUNDERBIRD452b1_2016051723_RELBRANCH as before
  • 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), alternative 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].
    • We are looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [2], bug 1145026.
    • 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, is mature. It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also Bug 1145026: 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.

2.x (Last, Current, Next)

2.40 current release

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

2.41 skipped

open tracking (0) tracking requests (8) targeted (0) fixed (26)

2.42 skipped

open tracking (0) tracking requests (8) targeted (0) fixed (21)

2.43 planned next release

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

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. Firefox has switched to https://discovery.addons. Instantbird points the URL to a chrome XUL document. If we do this we don't have to worry about the python stuff. The new Firefox discovery page will not serve up featured addons for SeaMonkey so we are sticking with services.* at least until they stop serving that up.
  • [Ratty] made some progress to fix bug 1222817 - Restore about:addons UI (Addons Manager) to old appearance. He found some useful ideas from the CSS in https://addons.mozilla.org/en-US/seamonkey/addon/classicish-addon-manager/ but currently doesn't have the time to continue.
  • [Ratty] will look at bug 995095 'Move the nsPlacesAutocomplete component to Suite'

Feature List, Planning

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

  • low triaging effort, above-average number of new bugs files.

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

Aqualon

Callek

ewong

frg

Waiting for review or feedback:

  • bug 521861 After creating news account through clicking news URL Account Wizard is broken.
  • bug 1055954 Popup exceptions are not added.
  • bug 1256714 Aero Peek not working. Filed bug 1269810 for zoom problem in m-r to m-c which I reproduced with FF 46.
  • bug 1272401 Port Firefox Bug 1241085 Parts 2 and 3, and maybe 4. Bug makes 2.46a1 unusable.
  • bug 1273240 XUL 'text-link' should open tabs rather than windows.
  • bug 1273682 Port Bug 1035125 to Seamonkey. Remove sandboxbroker.dll. Build break. Edit 05/22 fixed

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.

Titbits:

  • Started to look at Sync but don't hold you breath yet.

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. Adrian posted a build log and I looked at it. Seems to be l10n-merge related.
  • 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

InvisibleSmiley

KaiRo

mcsmurf

Misak

Mnyromyr

Neil

Px

Rainer Bielefeld

Ratty

  • Concentrating on doing reviews this current cycle.

Fixed:

  • bug 1116223 [Thunderbird] Move skin overrides to default theme chrome.manifest.
    • Also fixes: The chrome.manifest for the default theme is not packaged any more.
  • 🔒 Bug 👾👾👾👾👾 Destroyed all monsters . Monster Island is safe again for now.

Investigating:

  • bug 1267666 Trying to view or change Lightning extension options in Add-ons Manager hangs Seamonkey.
  • bug 995095 Move the nsPlacesAutocomplete component to Suite.
    • Mozilla-central bug 1223728 Removed the unifiedcomplete pref and the urlinline component. The remaining nsPlacesAutocomplete component will be removed too unless we move it to comm-central/suite/. Note we never used the urlinline component.
    • Alternatively use unified autocomplete by replacing autocompletesearch="history" with "unifiedcomplete". The latter includes history but with other stuff too.

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.

Other stuff:

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

Baroque Theatre, Laughing Gas, Dazzle Ships, Harems.

rsx11m

Pushed to comm-central:

  • bug 1269133 Remove add-on compatibility check from application update

Ready to land on comm-central, waiting for branch approval:

  • bug 1272888 Initial Mail & News window width and Preferences dialog can't accommodate Lightning elements, cut off contents
  • bug 1215150 Browser Preferences dialog's contents clipped at the right

Ready to land on comm-central, waiting for core patch:

  • bug 1269773 Remove Kinto and Safe-Browsing preferences from SeaMonkey's browser-prefs.js after they were moved to global all.js
    • patches in bug 1266235 dependent on finalized, yet waiting for those to check in again

Waiting for reviews:

  • bug 1265534 Make editor.CR_creates_new_p work for Mail & News composition and allow Paragraph mode as default
    • adopts new "compose HTML in Paragraph mode" feature from bug 330891 without making it the default
  • bug 1267631 Update the SSL/TLS Preference Pane once TLS 1.3 is implemented and ready for prime time
    • string changes only for now, TLS 1.3 has been enabled on trunk builds per bug 1250568

Preliminary patches:

  • bug 1271091 Uncloak the Geolocation preference UI for release builds once this feature is confirmed working
    • waiting for bug 903439 to enable this feature for SeaMonkey
  • bug 983689 With "Lightning" active: preferences window too big for netbook
    • respect actual screen sizes and provide scrollbars when necessary
    • still doesn't resize correctly for initial opening

Filed:

  • bug 1273298 Add-ons are disabled on trunk builds, claiming they could not be verified to work with SeaMonkey

Investigating:

  • bug 433001 Base default Mail & Newsgroup window size on available screen size

Other:

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

sgautherie

stefanh

tonymec

Any other business?

  • —
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2016-05-24&oldid=1134151"