You can update Adrians build to the official candidate 3:
https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/
Should behave way better than the May build I hope :)
.1 because Adrian built 2.49 from the comm-release branch and we wanted
to distinguish it from this one. All 2.49.1 ones are build from the
esr52 branch. 2.49.1 is at current esr52.4 level. The next release will
be .2 Hopefully when 52.5 arrives but depends on how long it takes to
bake a release and how much time ewong has. In any case there will be a
.2 at a future 52.x esr level.
FRG
Mason83 wrote:
On 08/10/2017 18:44, Frank-Rainer Grahl wrote:
Likely point 3 in the known issues in the 2.48 release notes:
https://www.seamonkey-project.org/releases/seamonkey2.48/
Fix will be in 2.49.1.
Maybe we should just drop the release notes and tell everyone to open a
lenghty thread in one of the support groups if he7she/it runs into a known
problem.... :)
FWIW, the problem still existed in 2.49.1 from 20170528045907
Which is expected since you FIXED the bug in August...
What does the .1 mean? When will it increase to .2?
Regards.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
