Intent to de-support: traditional add-ons
Walter L Schwartz
WaltS48 at comcast.net
Sat Oct 5 15:48:33 UTC 2019
You can follow along with the plans for SeaMonkey Extension
On 10/5/19 11:26 AM, Onno Ekker wrote:
> Op 5-10-2019 om 13:53 schreef Magnus Melin:
>> On 05-10-2019 13:37, Onno Ekker wrote:
>>> Can I have a little more clarification on this?
>>> As an add-on author, I always tried to keep my add-ons working during
>>> the daily/beta release cycle.
>>> I think you are telling us add-on developers now too, that it doesn't
>>> make much sense in trying to keep our XUL Legacy add-on or
>>> bootstrapped add-on compatible with Thunderbird 71.0a1 or later,
>>> because it won't work in Thunderbird 72.0a1 or 73.0a1 anyway, let
>>> alone in Thunderbird 78.
>>> Is that also what you implied?
>> Yes that is correct. Support for non-WebExtension add-on will be
>> dropped, so "keeping up" won't help, unless you convert it to a
>> supported format.
> And do you think SeaMonkey will follow suit(e)?
> I mean, they share your infrastructure, so they can't keep using
> And maybe there will ever be a SeaMonkey 2.57 or SeaMonkey 2.65, which
> will hopefully support the same add-ons as Thunderbird 60 and 68 does.
> But they can also stay on 2.49 and keep backporting security patches,
> but then they must probably do the same for a future
> addons.seamonkey-project.org or something like that...
> tb-planning mailing list
> tb-planning at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tb-planning