> I jumped on the ESR as soon as Adrian published it.
> The source code is ready, it just needs to be compiled.
Nope. Just found out the OS X bug wasn't fixed for 52. TB took it into a
branch. We need to do the same or maybe use the branch from the next TB which
should be due soon.
There were some real problems in early 2.49 builds. The last ones got just
fixed last week. Browsing was usually fine but mail had it share of them. Look
at reports for early TB 52 versions. A lot of unhappy campers out there. Most
were caused by changes in mozilla code which tightened security or just
changed something... Thankfully the TB devs fixed the nasty ones so that we
can profit from their work.
FRG
Mason83 wrote:
On 04/08/2017 14:34, WaltS48 wrote:
On 8/4/17 3:06 AM, Mason83 wrote:
On 04/08/2017 04:12, Edmund Wong wrote:
Frank-Rainer Grahl wrote:
It is probably bug 1286613:
https://bugzilla.mozilla.org/show_bug.cgi?id=1286613
Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
sure if we can backport all the parts to 2.48 and do a 2.48.1
It is worth doing that if it fixes problems.
Isn't it far simpler to push a 2.49.1 release?
How long did you have to wait for 2.48?
I jumped on the ESR as soon as Adrian published it.
The source code is ready, it just needs to be compiled.
I don't understand the difference between Adrian's builds
and official builds...
Regards.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
