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.
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.
> 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#s...
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 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#s...
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.
Jens Hatlak wrote: > 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#s...
> 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.
> 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.
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.
Phil
-- Philip Chee <phi...@aleytys.pc.my>, <philip.c...@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
> 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:
>> 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.
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.
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 wrote: >>> 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.
> 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.
> 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
What I can tell you is that 1.1.7 is very unstable. It totally crashed by test computer to the point I had to do a clean install.
Robert Kaiser wrote: >>> 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.
> 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.
> 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
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 wrote: > 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. :(
|
