Frank-Rainer Grahl wrote:
I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.
I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.
FRG
TCW wrote:
On 9/7/2017 1:26 PM, S Slicer wrote:
TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?
I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded. The only other 64-bit one that I have saved is 2.45.
That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the
Mozilla API decimation.
Forgive me if I have misunderstood the meeting minutes, but since the
nightly release channel will continue to support things like XUL
overlays, legacy extensions, webextension eperiments, etc. [0], why
don't you continue to ingest & build off of mozilla-central?
Is the plan to eventually switch back from ESR once bug fixes are landed
and the API removal spree has subsided? Or will the API changes break
more essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current
2.54 builds, which is a good sign.
Total removal of complete themes could be a larger issue, though.
Thanks for your continued support.
[0]: https://wiki.mozilla.org/Add-ons/Firefox57
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
