SeaMonkey 1.1.7 candidate builds - please help testing!
Robert Kaiser
You might have noticed recent posts about a Firtefox 2.0.0.10 being in
the works (<http://quality.mozilla.org/en/node/920>) and a test day for
that stability and security release
(<http://quality.mozilla.org/en/node/919>) and wondered if we'll do a
SeaMonkey 1.1.7 in sync with it.
And yes, you're right, we're planning to do this SeaMonkey 1.1.7 in sync
with the Firefox update, planned for next week (see
<http://wiki.mozilla.org/Firefox:2.0.0.10:Test_Plan#Schedule> for their
schedule).
A number of bugs will be fixed in this release, most notable we also
hope to have fixed the problems with launching SeaMonkey from read-only
installations, just like a Mac Disk Image.
Our candidate builds are now available at
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.7/
and we need your help to get good testing of them on all major platforms
before release.
Please help us with this testing so we can have a good SeaMonkey 1.1.7
release!
If you can do some smoketesting, please go to
<http://litmus.mozilla.org/> and do a SeaMonkey 1.1 test run
(<http://litmus.mozilla.org/run_tests.cgi?test_run_id=11>). For further
questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
other people around there who should know what can/should/needs to be
tested.
Thanks for your help,
Robert Kaiser
SeaMonkey Council member
Graham
> Please help us with this testing so we can have a good SeaMonkey 1.1.7
> release!
No release notes yet (404 "We're sorry, but we can't find what you're
looking for"). Other than that, no obvious problems so far.
Graham.
Geoff Welsh
>
> Our candidate builds are now available at
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.7/
> and we need your help to get good testing of them on all major platforms
> before release.
>
> Please help us with this testing so we can have a good SeaMonkey 1.1.7
> release!
runs fine here on OSX v10.4.11
thanks, KaiRo!
GW
Robert Kaiser
Yes, I still need to create those. Thanks for reminding me.
Robert Kaiser
Edward
dominique
Nothing to report so far, after half a day !
Dominique
Robert Kaiser
> Please help us with this testing so we can have a good SeaMonkey 1.1.7
> release!
Unfortunately, all Firefox and SeaMonkey testing did not reveal a
regression in canvas code (known one-line-fix forgotten to be included
in the code), we needed Firefox 2.0.0.10 to be in the wild for a few
hours to spot this. Nothing as bad as the last time something like that
happened, but still annoying enough.
As we caught it just the moment I wanted to move SeaMonkey files to
public, we'll respin builds and hope to get really fast QA to still
release this week, as it's already public that we have those three
vulnerabilities in 1.1.6:
http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.1.7
If you personally want to be on the safe side and don't need canvas
functionality, you probably should use the 1.1.7 candidates, but be
aware that they'll be replaced with new builds very soon. I'll announce
that here again when it's done.
Robert Kaiser
Jens Hatlak
> As we caught it just the moment I wanted to move SeaMonkey files to
> public, we'll respin builds and hope to get really fast QA to still
> release this week, as it's already public that we have those three
> vulnerabilities in 1.1.6:
> http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.1.7
I guess you won't wait for bug 376976, then? Just a question; I don't
know about the impact. I only saw it was checked in on trunk and read a
comment about it being prepared for branch.
Greetings,
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
Jose
What is regression in canvas code? Was Michaelangelo a cryptographer too?
Jose
Robert Kaiser
<canvas> is a HTML5 element we've implemented for some time now.
Robert Kaiser
Robert Kaiser
> Robert Kaiser wrote:
>> As we caught it just the moment I wanted to move SeaMonkey files to
>> public, we'll respin builds and hope to get really fast QA to still
>> release this week, as it's already public that we have those three
>> vulnerabilities in 1.1.6:
>> http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.1.7
>
> I guess you won't wait for bug 376976, then? Just a question; I don't
> know about the impact. I only saw it was checked in on trunk and read a
> comment about it being prepared for branch.
No, that's not on the radar. We won't unpackage the whole release
process, we'll add that one regression fix and be done. The bug you
mentioned hasn't even requested SeaMonkey approval yet.
Robert Kaiser
Peter Weilbacher
> As we caught it just the moment I wanted to move SeaMonkey files to
> public, we'll respin builds
If the canvas problem is really the only one that will be fixed by the
respin, you can still use the OS/2 builds that I have already emailed
you about because those are built without SVG and Canvas.
Peter.
P.S.: Is it not "respun"?
Philip Chee
> On 27.11.07 18:01, Robert Kaiser wrote:
> P.S.: Is it not "respun"?
I think that verbs are conjugated differently in German.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]The cost of feathers has risen. Now even down is up.
* TagZilla 0.066.6
Michael Wolf
> On Tue, 27 Nov 2007 21:42:42 +0100, Peter Weilbacher wrote:
>> On 27.11.07 18:01, Robert Kaiser wrote:
>
>> P.S.: Is it not "respun"?
>
> I think that verbs are conjugated differently in German.
No, it's similar. A direct equivalent for "respin" doesn't exist, but
for "spin". The German equivalent is "spinnen". Both the English and the
German verb are strong verbs:
English: spin - spun (also span) - spun
German: spinnen - spann - gesponnen
respinned is a form of a weak verb which is wrong here.
Robert Kaiser
> P.S.: Is it not "respun"?
Whatever. Redone. :p
Robert Kaiser
Ricardo Palomares Martinez
> Peter Weilbacher wrote:
>> P.S.: Is it not "respun"?
>
> Whatever. Redone. :p
>
LOL! :-)
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Robert Kaiser
>> release!
>
> Unfortunately, all Firefox and SeaMonkey testing did not reveal a
> regression in canvas code (known one-line-fix forgotten to be included
> in the code), we needed Firefox 2.0.0.10 to be in the wild for a few
> hours to spot this. Nothing as bad as the last time something like that
> happened, but still annoying enough.
We have new builds up at
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.7/
PLEASE help us testing them, so we can ship the release very soon now!
We already know we have those 3 vulnerabilities out in the wild with the
current stable version, which are fixed in this new SeaMonkey 1.1.7:
http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.1.7
In comparison with the last candidates, we additionally took a fix for
the <canvas> regression that forced the Firefox team to prepare a
2.0.0.11 release, and another small fix that makes our builds launch
correctly again from Mac disk images.
Release notes are prepared on
http://www.seamonkey-project.org/releases/seamonkey1.1.7/ already and
contain a fully list of fixed bugs in this release.
If you can do some smoketesting, please go to
<http://litmus.mozilla.org/> and do a SeaMonkey 1.1 test run
(<http://litmus.mozilla.org/run_tests.cgi?test_run_id=11>). For further
questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
other people around there who should know what can/should/needs to be
tested.
Robert Kaiser
SeaMonkey Council member
Rick
by test computer to the point I had to do a clean install.
Rick
Ed Mullen
Robert, if any of the devs have Comcast as their ISP please ask them to
email Comcast about their broken browser sniffing on their new
http://comcast.net page. It sees SM as not Firefox or any other
acceptable browser and redirects to a "Upgrade your browser" page. I've
emailed them a couple days ago but it still is broken. This started
happening after Comcast changed their home page but coincided with SM 1.1.6.
--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
I wonder how much deeper would the ocean be without sponges.
Edward
> Robert, if any of the devs have Comcast as their ISP please ask them to
> email Comcast about their broken browser sniffing on their new
> http://comcast.net page. It sees SM as not Firefox or any other
> acceptable browser and redirects to a "Upgrade your browser" page. I've
> emailed them a couple days ago but it still is broken. This started
> happening after Comcast changed their home page but coincided with SM
> 1.1.6.
Ed,
I have provided some information to Comcast, they are aware of it. But
as of this evening, I am still getting that browser upgrade page. :(
Edward
Rich Gray
>>> Please help us with this testing so we can have a good SeaMonkey
>>> 1.1.7 release!
Passed all, Mac OS X 10.5.1, Intel (executing out of a dmg, too!)
BTW, it's SeaMonkey 1.1.7 Reloaded. :)
--
Rich (Pull thorn from address to e-mail me.)
SeaMonkey - Surfing the net has never been so suite!
dominique
>>> Please help us with this testing so we can have a good SeaMonkey
>>> 1.1.7 release!
Hi Robert,
Works fine here with WinXP SP2, used with number of IMAP and
POP3 mail account, using IRC and Chatzilla,
No issue to report after a few hours use.
Dominique
dominique
>>> Please help us with this testing so we can have a good SeaMonkey
>>> 1.1.7 release!
Hi Robert,
Edward
>>> Please help us with this testing so we can have a good SeaMonkey
>>> 1.1.7 release!
No issues to report with the Linux version.
NoOp
Robert,
Why is it you always cross post these in the mozilla.support.seamonkey
group with followups set to mozilla.dev.apps.seamonkey?
I am sure that mozilla.support.seamonkey users may be willing to give
the build(s) a try & possibly even perform smoketesting (I've done so in
the past for most versions), but many mozilla.support.seamonkey users
may not even be subscribed to mozilla.dev.apps.seamonkey.
Please if you are to cross post the announcements, also notify
mozilla.support.seamonkey users that they should subscribe to
mozilla.dev.apps.seamonkey in order to read and/or continue any posts to
the thread.
That said, are you sure that you actually want
mozilla.support.seamonkey users over on the mozilla.dev.apps.seamonkey
group simply for reports regarding a new build test request? Perhaps a
separate mozilla.support.seamonkey might be a better idea?
Followup to this post set to: mozilla.support.seamonkey
Robert Kaiser
> Why is it you always cross post these in the mozilla.support.seamonkey
> group with followups set to mozilla.dev.apps.seamonkey?
Because netiquette says that it's bad to post without a followup to a
single group.
mozilla.dev.apps.seamonkey is for development and testing, while
mozilla.support.seamonkey is for end-user support. End users should be
notified that there are testing versions, but testers should always use
the dev group for test feedback, as everything but actually released
builds are development builds of some kind.
You might noticed that release announcements go the other way, with
followup set to the support group.
Robert Kaiser
NoOp
Thanks. However, in the future for users that are not subscribed to the
dev group, I'd suggest an added reminder notifying
mozilla.support.seamonkey users that they should subscribe to
mozilla.dev.apps.seamonkey in order to read and/or continue any posts to
the thread.
Downloading 1.1.7 now - sorry for the delay in testing, I've been
configuring new machines the past few days.
Gary