![]() All legacy add-on versions will be disabled in early October, 2018. On September 6, 2018, submissions for new legacy add-on versions will be disabled. Mozilla will stop supporting Firefox Extended Support Release (ESR) 52, the final release that is compatible with legacy add-ons, on September 5, 2018.Īs no supported versions of Firefox will be compatible with legacy add-ons after this date, we will start the process of disabling legacy add-on versions on (AMO) in September. IOW, so long as security is covered, there shouldn't be any immediate concerns.įor my needs, for the foreseeable future, you know where I'm at. Thunderbird, I'm not really familiar with, but, what, with TB 60, it is now "Quantum", or some sort of hybrid, not sure?Īnyhow, if that is the case, that is a newer ballgame for them, so relatively untested (as far as Quantum pieces are concerned). Hard for me to determine with no real forum, only reddit.) So if he is able to backport security fixes. Seemingly they are able to backport or otherwise secure PM, so that should not be an issue. ![]() (PM will argue otherwise, & yes, they're "right", but still it's essentially FF 52.) So if 2.49 or if 2.53 are able to get security updates, then there is less onus on 2.57. SeaMonkey 2.57 or whatever future version, is quite a ways off, if it ever happens. ![]() So if FF security updates are able to be backported to SeaMonkey, then for some period of time, that is all that really matters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |