SeaMonkey/StatusMeetings/2017-04-23

From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details

Agenda

  • Who's taking minutes? -> TBD
  • Nominees for Friends of the Fish Tank:
    • IanN for being our favorite reviewer

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

  • Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future.
    • frg did prepare a "asking for help" draft for the council. He is waiting for final comments and will be post it in the various SeaMonkey newsgroups. Some users are willing to proof-read and translate to other languages before it goes out. IanN will look at it after the meeting (done).
  • Mozilla plans to check in l20n. Unclear what this means for comm-central and the current l10n build configs. Needs to be monitored.
    • bug 1107635 - Rewrite build system l10n repack rules from Makefile rules into a Python script might also affect a timely l10n repack
  • Google API key for Safe Browsing V2, V4 and Geolocation. Ewong/Callek about getting it loaded onto the build machines.
    • Per bug 903439#c10, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key and so far received no response. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m fixed a bug to use the Google key for now in all trees bug 1352850.
  • IanN has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed.
    • TODO: Add Adrian Kalla to RelEng team. Overall no change as of today
  • IanN SeaMonkey project areas is very outdated. IanN plans to update the project areas soon.
  • Discussions and planning about the future of SeaMonkey and if we should set up own builders are still going on.
    • frg asked Adrian about his build config. He runs a small setup: 2 PCs, a Mac and a Jumhost (DD-WRT router). 1 PC is the Buildmaster and second the server with VMs for Windows and Linux building.
    • Ratty would like to have a try server.
    • frg misses an OSX try server most.
    • There would be problems uploading binaries to Mozilla servers. Linux distributors can upload crash-symbols. This would probably be possible.
    • An infra architect is now working for Thunderbird. The SeaMonkey project has gotten an invitation to join but nothing has been discussed yet. IanN asked ewong if he could get in touch with rkent. A new TB council has been elected and talks could start.
    • A joint discussion should take place. Not finalized who organizes this and when.
    • Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare.
    • Due to cost and availability the generation of daily builds would need to be cut back. The team doesn't see much problems here and a new schedule could be worked out.
    • IanN mentioned taskcluster as an alternative to buildbot. According to ewong and frg it looks complex and Mozilla specific.
      • The Thunderbird project plans to hire a designer for a new build infrastructure in the near future.
    • There are plans by Mozilla to do cross compiles on Linux for Windows and macOS. Not finalized yet.
  • —

CLOSED

  • —

Status of the SeaMonkey Buildbot Master and Tree

  • Various Bugs open for building.
    • OSX64: busted due to bug 1260362. Yasm 1.2 needs to be installed. (Ratty: Depends on bug 1257904. How to get traction on this?)
    • Linux64 Nightly: bug 1275215 is still open but Linux is building most of the time.
    • Linux64 build: bug 1275218 is still open but Linux is building most of the time.
    • Windows building is done on the loaner.
    • Various l10n and other bugs bug 1293943 which might also impact the release schedule.
      • CZ langpacks seem to be disabled by default, so that needs to be sorted.
      • DOMi still needs to be sorted.
      • Lightning l10n upload still needs to be sorted.
  • [23rd April 2017]
    • Tests have been re-enabled to enable us to find out what's busting them. bug 1295826 tracks the fixes for the Testing Infrastructure.
      • All tests are red.
    • All trees:
      • Linux*: busted due to bug 1350506. While it is 'fixed', the fix undid the mercurial upgrade. So I'll need to update the mercurial package somehow.
      • bug 1308923 might cause problems with 2.48 and 2.49. It is still unclear if it's fixed in later releases.
    • [comm-central]:
      • OSX64: green/orange
      • Win32: busted. Been working on the puppet issue that I've missed the builds.
      • See bug 1345770 for current breakages.
    • [comm-aurora]:
    • [comm-beta]:
      • OSX64: green/orange
      • Win32: busted. Been working on the puppet issue that I've missed the builds.
      • See bug 1334779 for current breakages.
    • [comm-release]:
      • OSX64: green/orange
      • Win32: busted. Been working on the puppet issue that I've missed the builds.
      • See bug 1319091 for current breakages.
    • [comm-esr52]:
      • No automation. [Filed bug 1352820]
      • Was broken by uplift of bug 1299500 for SeaMonkey only. Comment from libertyernie in bug 1353765 indicated that it fixed itself (Might have to do with unified sources).
      • See bug 1313304 for current breakages.
  • Notes:
    • Ewong did set up a cron job to do semi regular builds on the loaner machine. The MAC builders can be updated to OSX 10.9. He needs to consult with Callek first about this.
    • Windows nightly trunk builds are only done on the loaner. Migrating our Windows builders to Win2008 R2 will likely never happen.
      • 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.
    • 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.
  • See RelEng page for the RelEng status history.

Fixed Stuff Since Last Meeting

  • Google announced V4 of the safebrowsing api. Firefox adds support for it in bug 1167038 which is now mostly fixed. I think the part can be removed for now.
    • Works in SeaMonkey. No additional preferences are needed after rsx11m fixed bug 1352849 but for the V4 lists the Googgle API key needs to be on the server. The initial blocklists (unrelated item) were taken care of in bug 1358750.
  • —

Release Train

  • SeaMonkey 2.48 beta 1 released April 15, 2017 — kudos to ewong!
  • SeaMonkey 2.48 will be the next release tracked in bug 1351984 (general beta issues in bug 1328886).
    • ewong will start building 2.48 when he has the csets.
    • Updates from 2.39b1 apparently did not work, relevant for the 2.48 release to upgrade from 2.46 without problems. ewong is on it
    • l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
      • l10n problem is tracked in (bug 1231349).
      • Chatzilla and DOMi repack problems are also tracked in bug 1315552.
      • IanN has locale merge working for Chatzilla and is working on the DOMi repack issues.
      • See also bug 652063 (Enable localized ChatZilla builds).
    • Release notes in bug 1336315.
    • gtk3 will be disabled for 2.48 beta and release builds. It will be enabled for 2.49.
      • There are at least three problems with gtk3 builds which may not be resolved in time (bug 1269145, bug 1267982, bug 1331208).
      • A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version (bug 1312215).
      • Building releases with gtk2 is only a short time solution and will no longer be possible with Gecko 53 (SM 2.50, thus would still allow 2.49 gtk2 builds). Probably a meta bug for gtk3 compatibility should be created.
    • SeaMonkey 2.49 will be build with ALSA support. This has been disabled in Firefox 52 and causes problems for Linux users (see discussion in bug 1345661).
    • Because of the following bugs updates need to be tested if they are still working:
      • bug 1274722 Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
      • bug 1271761 Add CPU features/detection to update URL
    • 2.48 is still 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. bug 1254401
  • Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
  • ewong: Suggests the following:
    • Officially release a linux64 build (incl. tests)
      • Start with comm-central trunk.
      • Not entirely sure what is needed to make it official. Need to correspond with Callek.
    • Build an unofficial (contributed build) Win64 build. [akin to the status that Linux64 has now.]
      • Start later with comm-central we need to iron out the build issues, though right now, having just finished a W64 build; but I don't know how the tests are going to work though this will need to wait).
      • Currently tracked by bug 482143.
  • Current plan is to do releases off comm-esr52. No current backup plan other than continue building off comm-release.
    • Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [1].
    • Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
    • rsx11m filed bug 1358148 to get status and approval flags added in bugzilla for SeaMonkey
  • Useful Firefox Release Schedule link: Releases Scheduling
  • The next release after 2.48 will be 2.49.1 build from the ESR branch.
    • frg asked if a version of 2.49.x.x is supported to distingush between cycles and builds. tonymec thinks this might work but ewong isn't sure if the infra can cope with this.
  • Several languages seem to be no longer being updated and are missing many translations. They were removed from the website for 2.48 Beta 1. bug 1356294 tracks the removal from the build files.

Extensions and Plugins Compatibility Tracking

  • SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. This would fix long standing issues we have with AMO.
    • Ratty and IanN will meet with the AMO people to discuss this.
    • Ratty and IanN will meet with the Thunderbird people to discuss this.
    • [Ratty] Suggests that if we do this, we can also host the Firefox & Thunderbird Add-on Converter for SeaMonkey.
  • Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [2].
  • See Basics page. Please only list current changes here.
  • 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.
    • 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 [3], 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.
  • The HTML Validator adds HTML validation to SeaMonkey. The Beta version is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as the W3C validator but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See the developer's site for details.
  • In Gecko 52 obsolete toolkit parts were removed in bug 1312143. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and were fixed.

2.x (Last, Current, Next)

2.46 current release

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

2.47 skipped

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

2.48 planned next release

open tracking (0) tracking requests (3) targeted (2) fixed (23)

2.Next

  • We need someone to work on porting sync 1.5 over to replace legacy sync code. Frg was distracted by other bugs and tasks and didn't look into it yet.
    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.
    • As an alternative to porting sync setting up a sync 1.1 server might work.
    • Sync 1.1 has been removed from the mozilla source tree. If we want sysnc 1.1 to work we need to fork it.
      • Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system.
      • Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox).
  • 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:
    • —
  • Mozilla-central bugs that affect us:
    • bug 1298243 'drag/drop: DataTransfer.types is wrong type'. Building SeaMonkey still works but changes probably need to be ported.
    • bug 1276739 'replace list.txt with a region-aware JSON file format to allow different search configs...'. Regressions for SeaMonkey are tracked in bug 1300198.
      • bug 1300198 Move list.txt over to JSON once bug 1276739 is in.
        • This will likely break search engines and needs to be looked at.
    • 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 has been checked in and broke SeaMonkey 2.51. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite. Currently being worked on by IanN and frg for the Data Manager part.
    • 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. frg is currently looking into the patch from Neil.
  • [adriank] would like to drop DOMi or at least not bundling it with release builds in bug 1273222. Open for discussion.
  • [rsx11m] did open bug bug 1305902 for certificate pinning. Discussion if it should be enabled for SeaMonkey is still underway. Callek commented in the bug.
  • Nightly and Aurora updates are broken. bug 1321131 might be the cause. Aurora users need to be migrated to another channel if possible.

Feature List, Planning

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

  • low triaging effort, low number of new bugs filed.

Open reviews/flags: 38 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
  • 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:
  • Rainer started a Coffee-Mug-Competition. Please let any developers you know to it and post a big Help wanted! sign.
  • SeaMonkey Composer is outdated. Ratty thinks that using backports or parts of KompoZer [4] might solve some of the problems.
  • x64 Linux and for the first time x64 Windows builds will be made official as soon as possible.
    • Unofficial Linux builds just need to be declared official.
    • Providing Windows x64 builds is tracked in bug 482143.
  • The website and wiki are outdated. InvisibleSmiley no longer maintains the website. For 2.46 the website was updated but it still needs work.
    • bug 1253932 tracked the relnotes for 2.40 and could be used as a start point.
    • mcsmurf knows how to change the site.
  • frg suggested asking for donations in a future release. Probably during startup or more prominently on the website.
  • frg suggested a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
    • IanN suggests doing small patches which are easier to review.

Roundtable - Personal Status Updates

IanN will handle review requests. Ratty is currently absent.

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

Callek

ewong

frg

Waiting for review or feedback:

  • bug 912031 Removal of sync FormHistory api. Only test parts review missing. Filed bug 1346850 "guid in FormHistory notification "formhistory-remove" is always null" against toolkit.
  • bug 1282227 Port Bug 1071880 and Bug 1142937 to SeaMonkey: Notifiy users of slow addons. Unable to test. Either not working or I am missing something.
  • bug 1296839 Minor Tabbrowser.xml cleanups and changes. 1/3 still needs review?

Working on:

  • bug 521861 After creating news account through clicking news URL Account Wizard is broken.
  • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Unbitrotted the patch and did some changes but again get sidetracked and various build breakages.
  • bug 1256724 Update The Data Manager, and the Cookie Viewer so as to treat backspace and delete equivalently on Mac OS X. Took over the bug. Need to figure out some backspace problems in cookieviewer
  • bug 1293618 "Clear History from Private Data" completely broken (only test part left). A little on the backburner.
  • bug 1296850 Show standard loading indicator images in tab when busy or progress attribute are set. On the backburner. Need to look at the icons.
  • bug 1326377 Media view 'Save As ...' for embedded(?) picture fails. Need to find out how to get the private window status.
  • Did support stuff and working with ewong to get 2.48b1 out of the door.
  • Trying to clean up the shipped extensions build process so that they can be included / disabled via confvars.sh. Halfway done. No bug yet.

Titbits:

  • No time for Sync at the moment.
  • Helped ewong the get 2.48b1 out of the door and did mostly support and release stuff in the last two weeks. Some small bugs taken care of.

Other things on my mind:

  • --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. Will ask glandium about it.

IanN

Rainer Bielefeld

Ratty

rsx11m

Landed on comm-central:

  • bug 1352849 Enable SafeBrowsing v4 tables on SeaMonkey nightly builds
  • bug 1352850 Switch to Google for Geolocation services in all builds
    • should land on comm-beta and comm-esr52 as well (approvals pending)

Ready to land:

  • bug 1358316 Update System Requirements for Linux on seamonkey-project.org as they changed for 2.48

Filed:

  • bug 1354818 Project Dawn for SeaMonkey (remove aurora channel)
  • bug 1358148 Please add {tracking,status}-seamonkey-esr2.49 to the tracking flags and enable approval-comm-esr52 for SeaMonkey attachments

Still planning to look into:

  • bug 493217 add UI pref for media.autoplay.enabled
    • Move related items to a new Appearance → Media prefpane
  • bug 1318852 Make labels of cmd_properties action-oriented and context-sensitive, e.g. "Edit Contact", "Edit List", etc.
    • "real" fix

Awaiting new patch for ui-review:

Other:

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

stefanh

tonymec

  • Bug 1344411 - Lightweight themes are not supported anymore in SeaMonkey : RESOLVED FIXED, r=IanN, a(2.51)=IanN, 2.50-unaffected, 2.51-fixed, 2.52-fixed, verifyme
    • Patch written with much needed help by frg at start and finish, tested on Windows by frg and on L64 by me by hacking the omni.ja, awaits verification on both 2.51 and 2.52 on any platform by anyone willing. (Verification on non-Linux may require an owncompiled build.)

Any other business?

  • The next meeting will be held in two weeks: Sunday May 7, 2017, 14:00 UTC
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2017-04-23&oldid=1169056"