Robert Kaiser wrote:
Phillip Jones wrote:
SM2.0.1 was supposed to come out
the same exact time FF3.5.5 was to hit the streets.

FF 3.5.5 was a very short-cycle crash-fix-only release and we didn't
have the resources to create an update at that time (mostly because our
only build and release engineer, that is my humble self, was just about
to go into a vacation), so we still went with the regularly scheduled
security update as a base, which is today's FF 3.5.6 release.

And that's why SeaMonkey 2.0.1 has been in testing mode for about a week
now and just was made public (it's pretty normal to have 1-2 weeks of
testing phase before we make a release public, so that we can catch any
unexpected problems that might still be in the release builds).

Robert Kaiser
You actually have time for vacation?? :-)

I just update to 2.0.1 seems to cleared up a problem I turned into Bugzilla a week or two ago.

--
Phillip M. Jones, C.E.T.    "If it's Fixed, Don't Break it"
http://www.phillipmjones.net           http://www.vpea.org
mailto:pjon...@kimbanet.com
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to