Fx 52.9.0 TB 52.9.1
If we change the numbering scheme for 2.57 the still working classic
extensions would probably no longer work and would all need to be changed.
After 2.57 I am for aligning with TB instead of 3.x but rather unsure if we
will see a later version. source is being trashed more and more on a daily
basis. No chance to pick the good parts anymore or back out bad ones.
FRG
Daniel wrote:
Cruz, Jaime wrote on 3/08/2018 8:03 AM:
Ant wrote:
Thanks. Nice find and fix even though I never ran into this bug
since I use POP3 almost daily? :)
Since SeaMonkey's ESR60 version will be the next BIG jump for, why
don't they call it v3? It's a BIG jump and change like with
Firefox v52 to v60! Yeah, I'm not happy with the addon changes.
I'll lose a lot too! :(
Why not change the numbering scheme to keep it more in line with
Firefox ESR and Thunderbird? 52, 60, etc? Be a lot easier to keep
track of which level of code we're using...
Back in the "good ol' days, it was easy ... SM 2.48 was equivalent to FF
(2+48+1) 51. Not sure if that method still works now-a-days!
Is SM 2.49.4 equivalent to FF (2+49+1).4, i.e FF 52.0.4 or something??
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
