Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Support For SeaMonkey 1.x Dropped

4 views
Skip to first unread message

Robert Kaiser

unread,
Mar 16, 2010, 10:34:28 PM3/16/10
to
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more modern, but also maintained for
stability and security problems.

As the SeaMonkey 1.x series no longer receives security updates, due to
resource constraints, the SeaMonkey team strongly urges users of that
series to upgrade. Additionally, the team continues to strongly urge
people still using the old Mozilla Suite or Netscape 4, 6 or 7 to
upgrade to the new SeaMonkey 2.0 version. All these older software
packages suffer from a large, and steadily increasing, number of
security vulnerabilities because they are no longer being maintained.

Everyone on reasonably modern operating systems is urged to switch to
the newest release available for free download from the open source
project's website at www.seamonkey-project.org, providing the familiar
suite functionality in a remodernized application with additional
features and fully up to date security.
For the few who can't afford that, a last 1.x release is available.
SeaMonkey 1.1.19 does fix a few security issues, but not all known
security vulnerabilites, some of which may even be grave. Those are only
fixed in the new SeaMonkey 2.0, which will continue to be maintained for
quite some time and updated for any security issues as they might arise,
while the team is working on evolving the well-known suite even further
in future versions.

Full news article:
http://www.seamonkey-project.org/news#2010-03-16

Current version downloads:
http://www.seamonkey-project.org/releases/

SeaMonkey 1.1.19 downloads:
http://www.seamonkey-project.org/releases/1.1.19

Robert Kaiser
SeaMonkey project coordinator

Justin Wood (Callek)

unread,
Apr 1, 2010, 1:35:03 AM4/1/10
to
On 3/19/2010 11:41 PM, Justin Wood (Callek) wrote:
> On 3/18/2010 10:18 PM, Leonidas Jones wrote:
>> Rufus wrote:
>>> Rufus wrote:
>>>> Have upgraded my 1.1.1 install with 1.1.19, running SnoLep. No issues
>>>> so far...
>>>>
>>>
>>> ...make that 1.1.18.
>>>
>>
>> Do you have a a Panther or Jaguar machine up and running? If so, could
>> you try installing 1.1.19 on them?
>>
>> My experience is that SM 1.1.19 bounces in the Dock for a minute, then
>> crashes before opening.
>
> Ok, lets narrow down point of failure; if we can.
>
> Can you try loading the following on your mac (Where SeaMonkey 1.1.19
> doesn't work):
> * Thunderbird at
> http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/2.0.0.24/mac/en-US/
>
> * Firefox from a relevant build at:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.0.19-candidates/build1/
>
>
> Let me know your success/failure on both of those please.


Overheard on IRC... likely *is* relevant:

[20:37:24] <firebot> Thunderbird: 'MacOSX 10.5 comm-central check' has
changed state from Success to Test Failed.
[20:51:55] <justdave> TB 3.x run on OS X 10.3.9?
[20:57:07] |<-- ewong_w|afk has left irc.mozilla.org (Quit: Reboot.)
[20:59:10] -->| davida_ (das...@moz-B84BB441.stc.novuscom.net) has
joined #maildev
[20:59:28] |<-- davida_ has left irc.mozilla.org (Quit: davida_)
[21:00:44] -->| ewong_w|afk
(chat...@moz-E5D50C2E.static.netvigator.com) has joined #maildev
[21:01:09] |<-- davida has left irc.mozilla.org (Ping timeout)
[21:04:31] <BenB> justdave: same as the underlying Gecko/FF
[21:05:08] <justdave> yeah, found it on the momo/support site since I asked
[21:05:10] <BenB> justdave: i.e. 1.9.1 (IIRC) for TB 3.0, and 1.9.2 for
TB 3.1 and 1.9.3 for TB 3.2
[21:05:24] <justdave> told my mom she just needs to get a new computer. :)
[21:05:33] <BenB> justdave: :-(
[21:05:51] <BenB> I also have a PowerBook G4 12" and love it
[21:05:55] <justdave> she's getting SSL errors in TB 2.0.0.23
[21:07:06] <BenB> and you have reason to believe the client (and not the
server) is at fault?
[21:07:07] <justdave> which are mainly because NSS got upgraded in
2.0.0.23 without upgrading the UI for the certificate overrides
[21:07:15] <BenB> nod
[21:07:41] <justdave> so her choice is basically go back to 2.0.0.22 or
get 3.0, and she can't get 3.0 because her OS is too old
[21:07:53] <BenB> bummer
[21:08:14] <BenB> poor users

Summarized: NSS is to blame.

--
~Justin Wood (Callek)

0 new messages