The future of Seamonkey?

[vladmir]

https://blog.seamonkey-project.org/2016 ... the-music/
Face the music…
Posted on December 1, 2016

[rsx11m]

Updates on 2.46 and short-term future from yesterday's status meeting on https://wiki.mozilla.org/SeaMonkey/Stat ... is_meeting

As for 2.46, ewong will try to build it without any extensions (chatZilla, DOMi, and Lightning), and if that doesn't break localization again, proceed with those to get the update snippets done and push them to the update servers. From there, it will have to be sorted out why it still goes wrong on the Mozilla builders whereas local builds proceed.

It is increasingly likely that builds after 2.49 will come from the Gecko 52 ESR branch to get back to regular releases (and to avoid breaking support for Vista/XP and NPAPI plugins).

[tonymec]

Yeah, once the 2.46 release is out the door (without packaged-in extensions) the SeaMonkey RelEng team will get breathing space to find out the real cause of the l10n bustage.

[Frank Lion]

...the SeaMonkey RelEng team will get breathing space to find out the real cause of the l10n bustage.

Bet it's those grippies.

[ndebord]

Updates on 2.46 and short-term future from yesterday's status meeting on https://wiki.mozilla.org/SeaMonkey/Stat ... is_meeting

As for 2.46, ewong will try to build it without any extensions (chatZilla, DOMi, and Lightning), and if that doesn't break localization again, proceed with those to get the update snippets done and push them to the update servers. From there, it will have to be sorted out why it still goes wrong on the Mozilla builders whereas local builds proceed.

It is increasingly likely that builds after 2.49 will come from the Gecko 52 ESR branch to get back to regular releases (and to avoid breaking support for Vista/XP and NPAPI plugins).

rsx11m,

Good enough IMO. You can download extensions on your own and it will be good to get a browser that works with my financial sites (once again).

<g>

[Anonymosity]

Why does an external language pack work (with 2.47 anyhow), and built-in ones do not work?

[rsx11m]

Because repacking is broken within the build process as such.

[Frank Lion]

Updates on 2.46 and short-term future from yesterday's status meeting on https://wiki.mozilla.org/SeaMonkey/Stat ... is_meeting.

Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine.

That reads to me that when Firefox whacks XUL and extensions, then so too will SM?

[LuvKomputrs]

ewong is making progress!
We may be seeing a stable release of our beloved SeaMonkey very soon!
whoa

[LuvKomputrs]

SeaMonkey 2.46 Build 9 is available now and I've been using it with no issues at all.
Me thinks we'll get a stable release before X-Mas!
You can download the current build from here:
2.46 build #9

[johnduncan]

Updates on 2.46 and short-term future from yesterday's status meeting on https://wiki.mozilla.org/SeaMonkey/Stat ... is_meeting.

Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine.

That reads to me that when Firefox whacks XUL and extensions, then so too will SM?

That would be deal-breaking! XUL/XPCOM extensions are the life and soul of the suite, IMO. Really dumb move by Mozilla, if they go through with it; I think WebExtensions are already stable in FF, unfortunately...

[Peter Creasey]

XUL/XPCOM extensions

Can someone comment on what these extensions are for and what would be the implications if they are gone?

Thanks!

[WaltS48]

XUL/XPCOM extensions

Can someone comment on what these extensions are for and what would be the implications if they are gone?

Thanks!

See The Future of Developing Firefox Add-ons | Mozilla Add-ons Blog

There is a section about XUL/XPCOM.

The implications are extension developers have to convert their extensions to WebExtensions, new extensions must be WebExtensions, old abandoned, no longer updated extensions will no longer work unless someone decides to take on the task of updating it.

[Frank Lion]

XUL/XPCOM extensions

Can someone comment on what these extensions are for and what would be the implications if they are gone?

XUL/XPCOM extensions are what you know as, er, extensions - viewtopic.php?p=14722346#p14722346

In case it's not obvious, userChrome/Content.css would also get whacked at the same time.



Still, who knows, maybe the SM devs have a cunning plan up their sleeves to avoid all that, which is why I'm waiting for a reply to my post above from them.

[Scarlettrunner20]

XUL/XPCOM extensions

Can someone comment on what these extensions are for and what would be the implications if they are gone?

Thanks!

The author of Down Them All extension (which has over one million users) has written a scathing explanation (rant --- but worthy one IMO) for why he is abandoning his many years, most popular extension. Down Them All works great in Sea Monkey but it is an XUL extension. Nils Maier explains clearly and eloquently the plight of so many Firefox and SeaMonkey extension writers and why he and many others will be pulling the plug when Mozilla finally kills almost all extensions as we users have known them from the beginning with Mozilla Suite on to Firefox and Sea Monkey.

https://groups.google.com/forum/#!topic ... XzSt7iFl8g or read it at the author's website http://www.downthemall.net/ Extension is here also : https://addons.mozilla.org/en-US/firefo ... src=search

Several responses to his post which appear in another Mozilla News Group (Planning) mention his taking his extension to Pale Moon as it fully supports XUL extensions and has no intention of removing support or to Sea Monkey where it already works but there is the very real possibility that SeaMonkey will also kill XUL.