SeaMonkey/StatusMeetings/2016-05-10

From MozillaWiki
< SeaMonkey‎ | StatusMeetings
Revision as of 02:15, 8 May 2016 by Rsx11m (talk | contribs) (→‎rsx11m: added bug 1271091)
Jump to navigation Jump to search

« last meeting | index | next meeting »

SeaMonkey Meeting Details

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.
    • Update from Ewong: Hasn't received the key from mcsmurf yet.
    • Per bug 903439#c10, ewong has the Google API key (stating that for Geolocation service, not clear about Safe Browsing)
  • 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.
  • Next release will be 2.43 (no ETA yet).
  • 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).
    • lots of comm-beta bug fixes landed on THUNDERBIRD451b1_2016042214_RELBRANCH (for 45.1, mirroring comm-esr45) but not the default branch
      • Ratty has landed a bunch of patches from that branch on comm-release default
      • not clear about necessary calendar/ patches to build Lightning 48.b1 ourselves
  • Next mozilla-beta&arr;release migration is scheduled for May 30th, remaining merges for June 6th
  • 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).
    • [Fallen]: If you generate one using --enable-calendar, which produces all the locales similar to how this candidates directory looks like: http://ftp.mozilla.org/pub/calendar/lightning/candidates/4.5b1-candidates/ then I can upload that to AMO.
    • some patches which only landed on the Thunderbird 45.1b1 release branch may still need to be transplanted to comm-release default.
  • 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: 35 new, 4 fixed, 12 triaged.

  • medium triaging effort, above-average number of new bugs files (lots of which coming from bug 1268037, Help cleanup 2016).

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

IanN

InvisibleSmiley

KaiRo

mcsmurf

Misak

Mnyromyr

Neil

Px

Rainer Bielefeld

Ratty

rsx11m

Pushed to comm-central and comm-aurora:

  • bug 533984 Remove mention of Thunderbird in the description of the Lightning XPI
    • makes the description of the Lightning XPI generic and application independent as we intend to ship it with SM releases by default as well

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
  • bug 1267631 Update the SSL/TLS Preference Pane once TLS 1.3 is implemented and ready for prime time
    • string changes only for now, checkbox addition has to wait until core patches are landing
  • bug 1269133 Remove add-on compatibility check from application update

Preliminary patches posted (waiting for dependencies):

  • bug 1269773 Remove Kinto and Safe-Browsing preferences from SeaMonkey's browser-prefs.js after they were moved to global all.js
  • 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

Won't-fixed:

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

sgautherie

stefanh

tonymec

Any other business?

  • —
Retrieved from "https://wiki.allizom.org/index.php?title=SeaMonkey/StatusMeetings/2016-05-10&oldid=1131660"