SeaMonkey 2.0 Release Candidate 1
Robert Kaiser
the SeaMonkey website. We encourage testers to get involved in
discussing and reporting problems as well as further improving the product.
Full news article:
http://www.seamonkey-project.org/news#2009-10-10
Downloads for all available platforms and languages:
http://www.seamonkey-project.org/releases/2.0rc1
Release notes (preliminary ones for 2.0, RCs don't get separate relnotes):
http://www.seamonkey-project.org/releases/seamonkey2.0
System Requirements:
http://www.seamonkey-project.org/doc/2.0/system-requirements
Newsgroups: http://www.seamonkey-project.org/community#groups
File a bug: http://bugzilla.mozilla.org/enter_bug.cgi?format=guided
Get Involved: http://www.seamonkey-project.org/dev/get-involved
Robert Kaiser
SeaMonkey project coordinator
Ken Rudolph
> SeaMonkey 2.0 Release Candidate 1 is now available for free download on
> the SeaMonkey website. We encourage testers to get involved in
> discussing and reporting problems as well as further improving the product.
What's the difference between this and the actual release? Since
I'm not a techie, I chose not to be a beta tester; but I've been
waiting for the actual release, which I had heard was happening "in
a week or so". Apparently this still isn't the official release
version? When is that scheduled for? Or should I start using this
one now if I intend to go to 2.0 when it is released. I'm so confused.
--Ken Rudolph
Rich Gray
--
Rich (Pull thorn from address to e-mail me.)
SeaMonkey - Surfing the net has never been so suite!
Neil
> What's the difference between this and the actual release? Since I'm
> not a techie, I chose not to be a beta tester; but I've been waiting
> for the actual release, which I had heard was happening "in a week or
> so". Apparently this still isn't the official release version?
This is the first version that could technically become official. Until
then it's basically just another beta. Although we have hardened users
that test nightly builds which hopefully finds most of the major bugs,
it's only when we let all the beta testers loose on the release
candidate that we discover how reliable it actually is. After a week or
so, we'll decide whether or not it's ready; if it's not, we fix, or more
likely work around, as many bugs as we can and release another candidate
and repeat the process. Eventually (hopefully we run out of bugs before
we get bored of fixing them) we decide to make the latest candidate the
official released version. Any subsequent major bugs will then have to
wait for 2.0.1.
--
Warning: May contain traces of nuts.
David E. Ross
Was there a glitch in mozilla.dev.apps.seamonkey? Kaiser's original
message and every reply appears twice.
--
David E. Ross
<http://www.rossde.com/>
Go to Mozdev at <http://www.mozdev.org/> for quick access to
extensions for Firefox, Thunderbird, SeaMonkey, and other
Mozilla-related applications. You can access Mozdev much
more quickly than you can Mozilla Add-Ons.
David E. Ross
> On 10/10/2009 9:41 AM, Robert Kaiser wrote:
>> SeaMonkey 2.0 Release Candidate 1 is now available for free download on
>> the SeaMonkey website. We encourage testers to get involved in
>> discussing and reporting problems as well as further improving the product.
>>
>> Full news article:
>> http://www.seamonkey-project.org/news#2009-10-10
>>
>> Downloads for all available platforms and languages:
>> http://www.seamonkey-project.org/releases/2.0rc1
>>
>> Release notes (preliminary ones for 2.0, RCs don't get separate relnotes):
>> http://www.seamonkey-project.org/releases/seamonkey2.0
>>
>> System Requirements:
>> http://www.seamonkey-project.org/doc/2.0/system-requirements
>>
>> Newsgroups: http://www.seamonkey-project.org/community#groups
>> File a bug: http://bugzilla.mozilla.org/enter_bug.cgi?format=guided
>> Get Involved: http://www.seamonkey-project.org/dev/get-involved
>>
>> Robert Kaiser
>> SeaMonkey project coordinator
>
> Was there a glitch in mozilla.dev.apps.seamonkey? Kaiser's original
> message and every reply appears twice.
>
Oh! mozilla.dev.apps.seamonkey appeared twice in the Newsgroups
distribution list.
Philip Chee
>> Was there a glitch in mozilla.dev.apps.seamonkey? Kaiser's original
>> message and every reply appears twice.
>
> Oh! mozilla.dev.apps.seamonkey appeared twice in the Newsgroups
> distribution list.
SeaMonkey 2.0! Sugar and Spice and Everything Nice (plus Element-X)[1]!
Now with DOUBLE the goodness! So we have to announce this and to send
this out twice doubly in duplicate!
[1]
<http://media.photobucket.com/image/powerpuff%20ppz/Animegod500/Wallpapers/PowerPuffGirlsZ.jpg>
Mojo JoJo
--
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.
[ ]When uncertain, or in doubt, run in circles and scream: HEEELLLPP!
* TagZilla 0.066.6
Robert Kaiser
> Oh! mozilla.dev.apps.seamonkey appeared twice in the Newsgroups
> distribution list.
Yes, apparently I failed to change the second one to a "Followup-to" as
I had intended :(
Robert Kaiser
Robert Kaiser
> What's the difference between this and the actual release?
Only a few last-minute bugs fixes, which are hopefully very small and
fix things that users report with the RC1.
> but I've been waiting for the
> actual release, which I had heard was happening "in a week or so".
If we would release this RC as final, the release would be roughly a
week after it - I expect that we'll have a second RC though with a
number of assorted fixed, and I hope that one can become the actual
final around October 21.
> Apparently this still isn't the official release version?
It could be, but it might not yet be - that's what RCs are for, to get
some wide testing and last-minute reports of problem so that we see if
we can release exactly this build or need to do another one with some
last-minute bug fixes.
Robert Kaiser
chicagofan
> Ken Rudolph wrote:
>> What's the difference between this and the actual release?
>
> Only a few last-minute bugs fixes, which are hopefully very small and fix
> things that users report with the RC1.
>
Hopefully that will include the Address Book opening problem I still have with
RC1? :) The personal address book is selected, but won't open when I select
the Address Book from the tool bar.
This is my earlier message about it and Jens reply below:
>>> I should have said "when I am composing a message"... the following
>>> happens:
>>>
>>> When I click the "Address" icon on the toolbar, the address book opens to
>>> two "blank" fields. I have to click to open the drop down menu with
>>> "Personal Address Book" and "Collected Addresses"; then click to select
>>> my "Personal Address Book", to get the names in my address book to
>>> appear.
>>>
>>> In previous versions of SM, my addresses would be displayed when I
>>> clicked on the toolbar icon for "Address", because the "Personal Address
>>> Book" is *already* selected.
> <https://bugzilla.mozilla.org/show_bug.cgi?id=460550>
>
> In this case it was an obvious (JavaScript Debugger FTW) oversight so chances
> are the fix will still make 2.0.
>
> HTH
>
> Jens
A Williams
Hmmm, could that not be considered a bug?
If you have an address duplicated in the list of recipients, a really
clever mail/news client would warn you. Not that that will be in the RFC!
Robert Kaiser
> Robert Kaiser wrote:
>> David E. Ross wrote:
>>> Oh! mozilla.dev.apps.seamonkey appeared twice in the Newsgroups
>>> distribution list.
>>
>> Yes, apparently I failed to change the second one to a "Followup-to" as
>> I had intended :(
>>
>> Robert Kaiser
>
> Hmmm, could that not be considered a bug?
Not sure, but possibly. Can't harm to file it. :)
Robert Kaiser
Bob Fleischer
Well, I found that the visible difference between my production profile
and the virgin test profile is that I had "allow cookies for the
originating website only" on the production system (the one that
failed). I confirmed that setting this on the virgin system caused that
site to fail, also. I confirmed that changing the setting to "allow all
cookies" fixed my production seamonkey rc1 profile, too. So, is the
case closed?
However, just out of curiosity, I uninstalled Seamonkey 2 RC1 from the
virgin test system and installed Seamonkey 1.1.18 and found that the
banking web site works properly with either setting of "allow cookies..."!
Also, why does this setting make a difference between clicking a link to
open in the same window vs. opening in a separate tab or window (which
worked in SM 2 RC1 all along)?
So, I'm happy, but I do indeed wonder why this setting makes no
difference in the website behavior in SM 1.1.18, but obviously does in
SM 2 RC1.
(I could find no corresponding cookie setting in Firefox, so I couldn't
try this change in Firefox.)
Bob
Robert Kaiser
> Well, I found that the visible difference between my production profile
> and the virgin test profile is that I had "allow cookies for the
> originating website only" on the production system (the one that
> failed). I confirmed that setting this on the virgin system caused that
> site to fail, also. I confirmed that changing the setting to "allow all
> cookies" fixed my production seamonkey rc1 profile, too. So, is the case
> closed?
Probably, though that site relying on what at least looks like
third-party cookies seems bad, it's completely their issue if they do so.
> However, just out of curiosity, I uninstalled Seamonkey 2 RC1 from the
> virgin test system and installed Seamonkey 1.1.18 and found that the
> banking web site works properly with either setting of "allow cookies..."!
Not sure, but we had a number of changes to the cookie subsystem,
possibly also ones that make it more correct or whatever influences this.
> Also, why does this setting make a difference between clicking a link to
> open in the same window vs. opening in a separate tab or window (which
> worked in SM 2 RC1 all along)?
No idea, you probably need to ask the website designers.
Robert Kaiser
Bill Davidsen
> On 10/10/2009 9:41 AM, Robert Kaiser wrote:
>> SeaMonkey 2.0 Release Candidate 1 is now available for free download on
>> the SeaMonkey website. We encourage testers to get involved in
>> discussing and reporting problems as well as further improving the product.
>>
>> Full news article:
>> http://www.seamonkey-project.org/news#2009-10-10
>>
>> Downloads for all available platforms and languages:
>> http://www.seamonkey-project.org/releases/2.0rc1
>>
>> Release notes (preliminary ones for 2.0, RCs don't get separate relnotes):
>> http://www.seamonkey-project.org/releases/seamonkey2.0
>>
>> System Requirements:
>> http://www.seamonkey-project.org/doc/2.0/system-requirements
>>
>> Newsgroups: http://www.seamonkey-project.org/community#groups
>> File a bug: http://bugzilla.mozilla.org/enter_bug.cgi?format=guided
>> Get Involved: http://www.seamonkey-project.org/dev/get-involved
>>
>> Robert Kaiser
>> SeaMonkey project coordinator
>
> Was there a glitch in mozilla.dev.apps.seamonkey? Kaiser's original
> message and every reply appears twice.
>
--
Bill Davidsen <davi...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
Bill Davidsen
That would be a useful feature, I think ideally it would have three settings,
for warn and wait approval, for ignore, and for 'send just one copy' to avoid
some cases where [reply all] has the sender in the cc list.
Bill Davidsen
> SeaMonkey 2.0 Release Candidate 1 is now available for free download on
> the SeaMonkey website. We encourage testers to get involved in
> discussing and reporting problems as well as further improving the product.
>
> Full news article:
> http://www.seamonkey-project.org/news#2009-10-10
>
> Downloads for all available platforms and languages:
> http://www.seamonkey-project.org/releases/2.0rc1
>
than tracking the daily releases (as many of us have been doing).
> Release notes (preliminary ones for 2.0, RCs don't get separate relnotes):
> http://www.seamonkey-project.org/releases/seamonkey2.0
>
> System Requirements:
> http://www.seamonkey-project.org/doc/2.0/system-requirements
>
> Newsgroups: http://www.seamonkey-project.org/community#groups
> File a bug: http://bugzilla.mozilla.org/enter_bug.cgi?format=guided
> Get Involved: http://www.seamonkey-project.org/dev/get-involved
>
> Robert Kaiser
> SeaMonkey project coordinator
David E. Ross
> A Williams wrote:
>> Robert Kaiser wrote:
>>> David E. Ross wrote:
>>>> Oh! mozilla.dev.apps.seamonkey appeared twice in the Newsgroups
>>>> distribution list.
>>> Yes, apparently I failed to change the second one to a "Followup-to" as
>>> I had intended :(
>>>
>>> Robert Kaiser
>> Hmmm, could that not be considered a bug?
>> If you have an address duplicated in the list of recipients, a really
>> clever mail/news client would warn you. Not that that will be in the RFC!
>
> That would be a useful feature, I think ideally it would have three settings,
> for warn and wait approval, for ignore, and for 'send just one copy' to avoid
> some cases where [reply all] has the sender in the cc list.
>
See bug #522294 at <https://bugzilla.mozilla.org/show_bug.cgi?id=522294>.
Followup set to mozilla.dev.apps.seamonkey.