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.43a1 dated 9-Jan-2016 for L32 & L64, 6-Jan-2016 for Mac, and 2.42a1 dated 11-Nov-2015 for W32. No 2.44a1 yet, to parallel Firefox 47.0a1 which is being published every night (or every day depending on your timezone).

Release Train

Looks like ewong has managed to push 2.40 to the release servers at least for 2.40.

Discussion:

KaiRo: We should get a 2.42 release done based on Gecko 45 ESR and then only concentrate on getting nightly to build and run well and ignore everything in between for the moment. We can then do as many 2.42.x security updates based on ESR as we want before we get something out of nightly that is in good shape again.

Everyone agreed to skip 2.41.

Frg: Chatzilla locale generation still broken. Frg and Adrian to deal with this.

Carried forward from discussion at last meeting:

IanN suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta "release". L10N Translations might be problematic however rsx11m says using ESR would be "safer" with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some "deal" to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that's just simple patches such as label changes or adding a checkbox). rsx11m would go with {comm,mozilla}-esr45 and merge any "safe" patches from comm-beta but that may need some talking to l10n if string changes are involved.

Adriank thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.

SeaMonkey 2.39 was released November 8th, 2015.

SeaMonkey 2.40 final (tracking bug 1233615) was partially released March 14, 2016

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 SeaMonkeyhttp://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)

2.40

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 1254987 (Fix comm-central fallout from |bug 1254410 - Include app-specific configure files according to --enable-application/--enable-project|). All comm-central applications are not building due to bug 1254410 jcranmer, glandium, et all are looking into this.

Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles

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.

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.

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.

may prohibit Modern theme being shipped with or installed in SeaMonkey

removal is "decided" without any clear alternative envisioned

The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.

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. No one having objected (or even reacted), bug 1092632 is now RESOLVED FIXED. See its comment #18 for the announcement URLs.

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

[IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?

[frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.

[IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.

[IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB's new merged (c-c + m-c) repository?

[Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don't know how this will work.

[IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

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

Aqualon

Callek

ewong

busy getting 2.40 to worry about other stuff.

with the busted updates... even more busy.

frg

bug 1188348 data manager: domains invisible for Permissions, Preferences, Passwords. Contains string changes and hopefully will not miss the next cycle. I am done here and any changes will be need to put in new bugs.

bug 1251368 SeaMonkey cookie code needs to be updated to take into account mozilla-central bug 1245184. Might work whithout checking bug 1188348 in first but not tested. 2.44 and up affected.

bug 1250600 Update Safebrowsing in Seamonkey for recent changes in Firefox. Follow up bug of bug 920951 Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Old Seamonkey api key does no longer work but the lists are downloaded. Ratty found out that Google thottles in this case.

Working on:

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. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.

Otherwise didn't have much time in the last two weeks. Will see what I can do next.

Tidbits (didn't see the mentiond bugs changed since the last time):

Chatzilla imho only needs one more patch and it should build l10n for 2.41 and up:

bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content