Ant wrote:
On 12/1/2012 4:48 AM PT, Justin Wood (Callek) typed:
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.
They seem to be slow. :(
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.
Ah, that explains why no updates on my very old, updated Windows XP Pro.
SP3 machine. I saw it updated on my Debian stable box. I will check on
Monday then!
I noticed that too! Got the updates this morning for my two Ubuntu
machines, but none of my Windows machines are reporting an update is
available. First time I can ever remember seeing this happen!
--
Jaime A. Cruz
Secretary
Nassau Wings Motorcycle Club
http://www.nassauwings.org/
AMA District 34
http://www.AMADistrict34.com/
Pop's Run
http://www.popsrun.org/
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
