Discussion about Seamonkey builds
8 posts • Page 1 of 1
The SeaMonkey project is proud to present SeaMonkey 2.48 Beta 1:
If you hit the untrusted connection problem with a wrong https certificate when trying to download it you can get it directly from:
https://archive.mozilla.org/pub/seamonk ... es/2.48b1/
I really should put this into the release notes...
This is a Beta version mostly for testing purposes but it should be stable for general use.
If you are using Adrians 2.48 or 2.49 imho don't bother. Same if 2.46 works fine for you. Remember its a Beta so backup your profile. But if you test it we would be glad if you report any bugs you find. Please check the release notes for known problems.
If you are still on 2.39b1 (is still anyone using it at this point in time?) updates are not yet working. Ewong is trying to fix this. Because of a changed distribution server it would also impact 2.46 to 2.48 updates later if he does not succeed.
A regular 2.48 will follow (hopefully) soon. Afterwards we will switch to 2.49 ESR as fast as we can to be on par with Firefox ESR 52.
Been using this for a day now. So far no problems. To my surprise, all 9 of my add on's came over without any problems.
or even based on latest Firefox 52.1.0 Release ??
PS: Hopefully they will be able to fix this joking search engine bug
Yes, 2.48 is on par with Firefox 51.0.2 (or whatever the latest release on that branch was). After that, 2.49 will be released with current milestone (thus, 52.1.0 at the moment).
Well that is not exactly true for Beta 1. Beta 1 is based on the last beta source code before the Firefox 51 release and so more 51.0.0.
The 2.48 release is now being made and should hopefully be ready soon. It will be based on the latest 51 code available and so matches or surpasses the latest Firefox 51.
If the infrastructure doesn't give up before 2.49.1 ESR should then follow very soon
Yes, I was talking about the release.
>> Yes, I was talking about the release.
Ahh ok I see. Wasn't clear to me.
>> PS: Hopefully they will be able to fix this joking search engine bug
Its fixed and noted already in the 2.48b1 release notes as fixed.
Yeah, s/2.48 is/2.48 will be/ would have removed the ambiguity...
8 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest