All the builds for SeaMonkey 2.0.12 have been created (updates are
available on the betatest channel soon, going to beta as soon as I have
a few reports of the builds not being busted), so it's time for starting
tests on them to ensure we get an update out there that is worth
shipping to all our 2.0.x users.
Please help us testing the Windows installers, Mac disk images and Linux
packages, all available in 25 languages including US English.
The packages are available in the linux-i686, mac, and win32
subdirectories of
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0.12-candidates/build1/
Once again, the linux-x86_64 build is NOT OFFICIAL and NOT ENDORSED. It
will be listed as "contributed build" even if it was technically created
by our build system, and it will be treated in no other way than usual
contributed builds. In other words, it's just an experiment.
Please use the builds for any usage patterns you can think of, possibly
also doing a https://litmus.mozilla.org/run_tests.cgi?test_run_id=7
smoketest run on them. I know that Litmus run isn't perfect, but it's
the best we have right now.
Localizers, please test the builds in your locale, any updates can be
taken with further sign-offs (in the new tool) for 2.0.13 and future
updates.
If no problems come up in testing those builds, they will probably go
live as the official 2.0.12 on February 8, in sync with Firefox and
Thunderbird updates that will fix the same set of security issues.
The list of bugs fixed in this update contains 29 public reports thus
far, 27 security issues are currently hidden and only to be disclosed
upon release of our updates. The bug query to find the issues is
https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&product=Testing&product=MailNews+Core&product=SeaMonkey&product=Other+Applications&field0-0-0=keywords&type0-0-0=anywords&value0-0-0=fixed-seamonkey2.0.12&field0-0-1=cf_status_191&type0-0-1=anywords&value0-0-1=.17-fixed&field0-0-2=cf_status_thunderbird30&type0-0-2=anywords&value0-0-2=.12-fixed
--
Justin Wood (Callek)
Using it now for 3days as my everyday work browser on Vista SP2 without
issues.
Only the copyright on the about: page still is "2010"...
Building and testing on AIX was successful, too.
--
Uli Link
--
~Justin Wood (Callek)
> I wonder if anyone has yet tested the updates, so far that is our
> largest need in testing this release.
My W2K installation updated itself, although I didn't wait for it to
offer the update.
--
Warning: May contain traces of nuts.
Works:
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.17)
Gecko/20110123 Lightning/1.0b1 SeaMonkey/2.0.12
Have you tried it?
From: "Justin Wood (Callek)" <Cal...@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13)
Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
Yes, c.f. my original announcement post :-P
[Again, I tell you I'm not ALWAYS posting to NG's from SeaMonkey]
--
~Justin Wood (Callek)
Updated through the beta channel just yesterday:
Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9.1.17) Gecko/20110123
Lightning/1.0b1 SeaMonkey/2.0.12
No issues so far.
You pushed to beta, so people on the beta channel are getting it
already. On Friday, we had 481, on Saturday 453 installations of 2.0.12
that were being used. Not getting a lot of bug reports about that could
mean that testers are satisfied so far. ;-)
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community needs answers to. And most of the time,
I even appreciate irony and fun! :)
Well, I was more looking to see if anyone who was on the beta channel
was watching newsgroups and could "report" on it, but certainly no news
is good news when we have stats. :-)
--
~Justin Wood (Callek)
Justin Wood (Callek) a tapoté, le 29/01/2011 22:41:
> I wonder if anyone has yet tested the updates, so far that is our
> largest need in testing this release.
I've tested it on Windows Xp Home.
--
Stéphane
http://pasdenom.info
Yes, I know it's a bit pedantic. But I think that when you post these
notices it couldn't hurt to switch to SeaMonkey to do so (and
particularly the version you are asking other to test).
The fact that you continue to post these notices with Thunderbird rather
than SeaMonkey doesn't bode well for users (particularly in the users
support group) & gives the indication that you prefer Thunderbird rather
than SeaMonkey for your preferred news/mail application. Any particular
reason that you've never (that I know of) posted the notices from SeaMonkey?
Opps, my mistake:
"Any particular reason that you've never (that I know of) posted the
notices from SeaMonkey?"
should have read:
"Any particular reason that you've never (that I know of) posted the
notices from the SeaMonkey version that you are asking others to test?"
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.17) Gecko/20110123
SeaMonkey/2.0.12
P.s. I did get an automatic update for the DOM inspector pushed
to me on 2/13/2011.
--
Rostyk
Our 2.0.12 release is bound to the also planned Firefox updates because
we ship the same security updates there, and we only can make public
what those are when the millions of Firefox users (compared to our
thousands) also have security updates available. Unfortunately, there
was a somewhat lengthy investigation of strange crash patterns in
Firefox releases that made us hold those for a while, but after we
cleared that what we saw was not a new issue, all those releases,
including SeaMonkey 2.0.12, should now happen tomorrow, March 1st.
> Moreover I see here discussions of 2.0.13 pre.
That's because the 2.0.12 builds have already been generated and so
nightlies from later code already are pre-2.0.13 builds.