SeaMonkey 2.0.14 has been released!

[rsx11m]

Official announcement and release notes:

• http://www.seamonkey-project.org/news#2011-04-28
• http://www.seamonkey-project.org/releases/seamonkey2.0.14/

Security fixes:

• http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.14

The next release should be SeaMonkey 2.1 final, I'm sure looking forward to it!

[therube]

(I opened SeaMonkey 2.0 just before & it said 2.0.15pre .)

> The next release should be SeaMonkey 2.1 final, I'm sure looking forward to it!

Me too. Kind of.
But I fear there will be far more issues going from 2.0 to 2.1 then there were going from 1.x to 2.0.
Upgrade aside, I fear the rock solid stability we are accustomed to is going to falter.
And IMO I think its becoming a bloated pig, using more resources then 2.0.

And I'm stuck with an early March build. Anything later crashes on me on startup (using my existing Session Restore).

Maybe that's a bit harsh. Maybe I just keep too much damn crap open at once.

[rsx11m]

Hmmm, the 2.1pre nightly builds work fine for me, I'm wary of the 2.2a1pre trunk builds which aren't quite focused on yet and subject to heavy movement on the mozilla-central side. As for stability, it will have to be seen how the new release scheme Firefox 5.0+ imposes on the other applications (no more minor releases other than oilspills, thus no frozen API for a branch and features can change from release to release in backend and UI) will work out for SM 2.2 and later, that's more what I'm concerned about...

The problem with SM 2.0.x will be that the Gecko 1.9.1 will officially retire soon (basically with today's releases), thus SeaMonkey would have to take care themselves of any security backports to that branch.

[Peter Creasey]

I fear there will be far more issues going from 2.0 to 2.1 then there were going from 1.x to 2.0.
Upgrade aside, I fear the rock solid stability we are accustomed to is going to falter.
And IMO I think its becoming a bloated pig, using more resources then 2.0.

Egads! What a scary scenario!!

[rsx11m]

I'd dare to suggest that the bulk of any bloat comes from the core code mostly maintained by the Firefox people. There certainly are new major features (like the Data Manager) in SeaMonkey 2.1 as well, and quite a few fixes/enhancements from the mail/news code shared with Thunderbird, but I wouldn't see those as a major factor in any possible bloating.

[therube]

I'd dare to suggest that the bulk of any bloat comes from the core code mostly maintained by the Firefox people.

Right.

I am regularly using 1 GB of memory for the browser, & then plugin-container.exe is using another 2-300 MB on top of that. After a bit of time, things get quite lethargic. What should be a crisp action, sees a delay. 2.1 seems to be using more memory then 2.0, seems to be negatively affected sooner then 2.0.

Perhaps with maturity, tuning, more bug fixes ...

(Think about the times when people used to complain, oh, I'm using 100 MB of memory ...)

[rsx11m]

And I'm stuck with an early March build. Anything later crashes on me on startup (using my existing Session Restore).

BTW: Did you try a fresh install and/or a new profile?

[Philip Chee]

And I'm stuck with an early March build. Anything later crashes on me on startup (using my existing Session Restore).

BTW: Did you try a fresh install and/or a new profile?

I think he's tried everything short of sacrificing a chicken over the SCSI chain.

Phil

[therube]

I'm sure a new Profile will work.
What does not work, is starting (attempt to at least) with my existing Profile, existing sessionstore.js.
I get up to ~1.6 GB of memory usage, then crash. Repeatedly. Up to & including a build of April 29.

Everything the same works on a March 5 build.
Well there is one difference, BarTab works in the March 5 build, but not in current builds.
If I disable in March 5 ...

EDIT: Crashed also. That sucks.

[LuvKomputrs]

Official announcement and release notes:

• http://www.seamonkey-project.org/news#2011-04-28
• http://www.seamonkey-project.org/releases/seamonkey2.0.14/

Security fixes:

• http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.14

The next release should be SeaMonkey 2.1 final, I'm sure looking forward to it!

I'm also looking forward to the final release of 2.1.

[4td8s]

The problem with SM 2.0.x will be that the Gecko 1.9.1 will officially retire soon (basically with today's releases), thus SeaMonkey would have to take care themselves of any security backports to that branch.

well Gecko 1.9.1 on the FF 3.5 side has already been retired as of this notice in early May since FF 3.5.19 came out.

though I wouldn't be surprised if there was just one more SM 2.0.x release (aka. 2.0.15) before the SM 2.0 series gets retired. I see from this bugzilla search of at least 12 bugs fixed in 2.0.15.

[Uncle Spellbinder]

Been using betas for months now. I just LOVE it. Nice to see final finally out! Great work, devs!

[CMonkeyBloke]

Been using betas for months now. I just LOVE it. Nice to see final finally out! Great work, devs!

Yeah, I've been using the betas since they appeared. I think that the final is great. I hope some themes are compatible soon, I do love Kairo's Early Blue.

[rsx11m]

though I wouldn't be surprised if there was just one more SM 2.0.x release (aka. 2.0.15) before the SM 2.0 series gets retired. I see from this bugzilla search of at least 12 bugs fixed in 2.0.15.

There haven't been any 2.0.15pre nightly builds since June 6th, and all resources are going right now to the 2.2 release which will contain the same bug fixes, thus I would rather be surprised if there is a 2.0.15 release. On the other hand, Firefox still maintains their 3.5.x nightly builds, so who knows if they are going to release a 3.5.20 or not (nothing scheduled).

[James]

There is a Firefox 3.6.18 release planned for June 21 same as Firefox 5.0 and ThunderBird 3.1.11 however from what I have see Mozilla is not planning to release any more Firefox versions on the old 1.9.1.* branch. The mozilla-1.9.1 branch nightlies get changed to next version during/after release and the builds are automatic.

Also it is Mozilla (not Firefox the web browser) maintaining the 3.5.x nightly builds.


update: no mention of Firefox 3.5.20 at https://wiki.mozilla.org/Firefox/Planni ... ta_.285.29 and earlier.