SeaMonkey/StatusMeetings/2016-06-21

From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details

Agenda

  • Who's taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • rsx11m for fixing some frontend things.

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 just announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in bug 1167038.
  • Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
    • Per bug 903439#c10, ewong has a Google API key (stating that for Geolocation service). Safe Browsing 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.
  • IanN SeaMonkey project areas is very outdated. There just aren't enough people to go around. We probably need to reduce the number of areas or group them together.
  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • frg and Rainer_Bielefeld have offered to help KaiRo with the de locale translation.

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. He is still unable to set a timeframe for the next release. The moco build system is constantly changing. The MAC builders can be updated to OSX 10.9. He needs to consult with Callek first about this. He has trouble building the Windows version on the loaner.
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2015 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Langpacks aren't updated when auto-updating SeaMonkey because they aren't uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
    • Various Bugs open for building OSX and Linux.
    • The team is unhappy with the current build bot situation but still commited to get it resolved as possible. It was suggested that the unofficial adriank builds might somehow be uploaded as official builds until the build bots are fixed. adriank will speak with Callek if this is possible.
    • [21st June 2016]
      • [comm-central]
      • [comm-aurora]
        • All platforms (Nightlies): busted due to the crash-symbols token needs updating. [Fixed]
      • [comm-beta, comm-release]:
        • Aside for the Windows-monkey-on-my-back bug 1271903, these trees haven't been infected by the bustage that has infected c-c and c-a (yet). [Give them time... I'm sure that can be 'fixed'.]
  • See RelEng page for the RelEng status history.

Fixed Stuff Since Last Meeting

  • Nothing new here

Release Train

  • Next release will be 2.44 (no ETA yet). 2.43 will be skipped also.
  • bug 1234012 will be backed out in a special m-r release branch for Seamonkey 2.44. This seems to cause major problems for Enterprise users in Firefox but will not be backed out there.
  • 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.
  • comm-beta is back on the regular track with TB 47.0b1 having been tagged.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addons are now compatible by default. The code in the addon manager that complains about incompatible version numbers has been removed. This should reduce the friction of installing older addons.
  • Addon Compatibility Listings (outdated), alternative list started (currently Rainer Bielefeld is the only active maintainer)
  • 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 (1) fixed (21)

2.43 skipped

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

2.44 planned next release

open tracking (0) tracking requests (1) targeted (1) fixed (20)

2.Next

  • We need someone to work on porting sync 1.5 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].
  • In progress.
    • bug 1274722 Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
    • bug 1271761 Add CPU features/detection to update URL
  • 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.
    • Rsx11m filed bug 1267631 Update the SSL/TLS Preference Pane once TLS 1.3 is implemented and ready for prime time.
      • There is still considerable activity in TLS 1.3 core work. We can check it in and allow users to enable it for testing, then hope it'll be ready when trunk hits release. Since the strings are in already, we are flexible.
  • 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: 30 new, 13 fixed, 9 triaged.

  • low triaging effort, larger than average number of new bugs files.

Open reviews/flags: 63 review 5 super-review 2 ui-review 12 feedback

  • 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 1055954 Popup exceptions are not added.
  • bug 1256714 Aero Peek not working. Filed Firefox bug 1269810 for zoom problem in m-r to m-c which I reproduced with FF 46 and 47.
  • bug 1272401 Port Firefox Bug 1241085 Parts 2 and 3, and maybe 4. Bug makes 2.45 and 2.46 unusable. url bar does not change.
  • bug 1278130 Port Bug 1273685 PopupBlocking:UpdateBlockedPopups messages can be very large to Seamonkey.
  • bug 1278633 about:performance not working in Seamonkey.
  • bug 1279206 Password icons.

Working on:

  • bug 521861 After creating news account through clicking news URL Account Wizard is broken.
  • 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:

  • Nasty webm problem in 2.44 and up: bug 1279851 CRASH when benchmarking webm decoding performance on YouTube page.
  • Started to look at Sync but don't hold you breath yet.

Other things on my mind:

  • Please lets do something about the infrastructure. This su*cks!
  • Seamonkey compiles fine with VS2015 Update 3 RC. Update 3 uses a new optimizer per default which so far doesn't seem to cause any visible problems in daily browsing.
  • --enable-optimize=-O2 should be used for Windows release builds. Linux gcc --enable-optimize optimizes for speed. With 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

currently working on


Might be worth to be discussed
Questions
  • SeaMonkey Help
    • thoughts concerning "bug 1279416 - Decide how to handle User Documentation what has been moved to www-archive.mozilla.org"?
  • SeaMonkey Localization
    • My experience from Help cleanup: there is absolutely no clear proceeding how localization teams get knowledge concerning code changes with relevance for their area and how a tracking for fixes of every affected language can work; and it's completely useless to ask (mozilla.dev.l10n, ...), they don't know themselves. If there is no suggestion for a different solution what will work, creating separate localization Bugs for every affected Language with word "SeaMonkey" in Summary is the the only known method what allows systematic work. Thoughs? Suggestions?

Ratty

  • Concentrating on doing reviews this current cycle.

Investigating:

  • bug 1222817 Restore about:addons UI (Addons Manager) to old appearance by overriding Toolkit's Project Chameleon styles.
  • bug 1267666 Trying to view or change Lightning extension options in Add-ons Manager hangs Seamonkey.
  • bug 1268970 All mochitests fail with: IOError: [Errno 2] No such file or directory: u'c:/t1/hg/comm-central/mozilla/obj-i686-pc-mingw32\\_tests\\testing\\mochitest\\runtests.py'.
  • bug 1280698 Package EmojiOne TTF font on Linux and Windows.

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 1276458 Update all existing callers of nsICookieManager2.add() and nsICookieManager2.getCookiesFromHost() to make them origin attributes aware.

Fixed:

  • bug 1276951 add --enable-calendar to mozconfigs now that we are shipping Lightning with SeaMonkey (also disable addon signing requirements and package js-shell)
  • bug 1277293 Replace getSimpleCodebasePrincipal with createCodebasePrincipal (SeaMonkey Part).
  • bug 1277299 Replace getSimpleCodebasePrincipal with createCodebasePrincipal (Thunderbird Part).
  • bug 1277305 nsDragAndDrop.js: fix trailing spaces (Bug 1245649: Turn on no-trailing-spaces) plus followup to bug 1174601

In Progress:

  • bug 995095 Move the nsPlacesAutocomplete component to Suite.
    • bug 1281005 Move the nsPlacesAutocomplete component to Suite (mozilla-central part).
    • 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.
  • bug 1222818 Restore about:support UI (Troubleshooting Information) to old appearance by overriding Toolkit's Project Chameleon styles (revert bug 1161156 for SeaMonkey).
  • Classic and Modern theme: CSS styles for about:networking.

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/aurora/beta:

  • bug 1280058 Warning for destructive retention settings for POP and IMAP accounts shouldn't be shown for Local Folders (MailNews)
  • bug 1274722 Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
    • patch by rstrong, adapted from Firefox patch in bug 1271761

Pushed to comm-central:

  • bug 1265534 Make editor.CR_creates_new_p work for Mail & News composition and allow Paragraph mode as default
  • bug 1275941 Trim white-space characters from calendar.useragent.extra to avoid redundant spaces in the user-agent string (Calendar)

Ready to land:

  • bug 1267631 Update the SSL/TLS Preference Pane once TLS 1.3 is implemented and ready for prime time
    • string changes have landed, TLS 1.3 was enabled on trunk builds per bug 1250568
    • still somewhat uncertain when the checkbox should be exposed, activity is ongoing

Waiting for reviews:

  • bug 1275679 Add option to the HTTP Networking preferences to disable Lightning user-agent addition
    • counterpart of the Firefox checkbox now that Lightning is bundled by default

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

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-06-21&oldid=1138571"