SeaMonkey 2.38

SeaMonkey 2.38 has been released.

’nuff Said. 🙂

:ewong

24 Responses to SeaMonkey 2.38

  1. Thanks for the work! It’s great to see Seamonkey on track again.

  2. When will there be proper release notes?
    It’s the 2nd release without them.

    Is this a new trend, following Window 10 example?

  3. 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.

Leave a Reply

Your email address will not be published. Required fields are marked *