Ant wrote: > but no internal updates yet. Indeed.
Symantec again, they changed their internal process on us, and our builds themselves were ready late thursday, while I was hoping that Symantec would get back to me with a "we have whitelisted you" on Friday, it seems they did not. I plan to (within the next 24 hours): * Install the stable 2.14 ** Update it to 2.14.1 (by setting myself onto the "releasetest" update channel manually) ** See if my local, up-to-date copy of Symantec gives us the same issue we have seen in the past. * if it gives NO ISSUE, I'll push all updates live * if it CONTINUES to give us an issue, I'll: ** Manually split out windows from the update snippets ** Push all other OS snippets ** and ONCE SYMANTEC SAYS WE ARE WHITELISTED push the windows snippets [likely monday] There is no Security implications in this release, it merely corrects a few crashes and a few (relatively minor, but visible) bugs/compatibility. There were major drivers on the Firefox side that do not affect us, though since at least one of the major crashes could easily affect us, I chose to continue to release this update. I mentioned re: Security so you know there should be no worry about using 2.14 even without 2.14.1 in the meantime. -- ~Justin Wood (Callek) _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
