SeaMonkey 2.38 has been released.
’nuff Said. 🙂
:ewong
-
Recent Posts
Recent Comments
- Ronnie on 2.40 is out!
- rsx11m on 2.40 is out!
- Markus on 2.40 is out!
- d4rkn1ght on 2.40 is out!
- George on 2.40 is out!
Archives
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- April 2015
- August 2014
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- October 2011
- September 2011
- August 2011
- June 2011
- April 2011
- March 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- July 2009
- June 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- April 2006
- February 2006
- January 2006
- December 2005
- November 2005
- September 2005
Categories
Meta
what happend with the versions 2.36 and 2.37?
Those were skipped, see e. g. https://wiki.mozilla.org/SeaMonkey:Home_Page
Thanks for the work! It’s great to see Seamonkey on track again.
When will there be proper release notes?
It’s the 2nd release without them.
Is this a new trend, following Window 10 example?
Next they’ll remove all the buttons and all the options too!
What the **** is going on with the last release??? NOTHING works properly… neither passwords being on “remember” nor youtube full screen function… it is really disgusting! For what reason do you release an update which only messes up everything? Don’t you test anything before a realease? I’m really pissed off and thinking about not using Seamonkey anymore! With each update during the last time the troubles extend! That shouldn’t be the intention of an update… you guys should think about releasing bullshit! Better keep a functionable version until you are able to release something working without trouble EVERYWHERE!
This reminds me of https://bugzilla.mozilla.org/show_bug.cgi?id=1202282#c20.
I understand the frustration with SeaMonkey’s problems and there are a lot of them. It is not our intention of releasing problematic releases. Since the Rapid Trains method of releasing hit, we’ve been trying to keep up with the pace and it isn’t easy. Things keep on slipping between the cracks and only when it gets released do we know about the problems.
We are doing the best we can with whatever resources we can afford. We’re working hard in getting releases out AND getting the code fixed; but I understand at this point, it’s not enough. With Sync completely busted, it makes this even more painful.
We do appreciate you posting your opinion here.
However, that said, while I understand the frustration, we really don’t appreciate reading profanity on this blog. It’s really unnecessary. There are ways to express your frustration or dissatisfaction. Profanity is not one of them.
Thank you for your comments though. I’ll discuss this with the rest of the crew and see how things go.
Maybe the team should look at the example of Pale Moon who are now developing a Gecko-like engine, in order to keep what used to be the best part of Firefox: ability for customization (XUL and XPCOM).
SeaMonkey used to be great until the (not so) recent race of FF to become a Chrome clone. Now, the need to “keep up” with that speed-development does bad things.
I can only speak for myself, but I prefer bug fixing, and some long-term direction plan instead of this chase ofter FF.
As I asked on another post, having some idea of a future plans for this browser, is desperately required.