SeaMonkey 2.39 is out

Compared to 2.38,  this was a bit of a struggle to get 2.39 done.  Made some mistakes along the way; but, with a sigh of relief, SeaMonkey 2.39 is out.

Now, on to getting the infra back on track… a very slow and albeit, overwhelming at times, process.

I’m sure everyone has had the feeling.  Kind of like sitting at a desk, and having a whole pile of paperwork/homework to do and not knowing where to start since they seem to have their hands up saying “I’m important! You need to finish me first!”  Know that feeling?

And it doesn’t help it that Trunk is now busted.

:ewong

About ewong

I'm a SeaMonkey dev/RelEnger and a bit of a buildbot dev.
This entry was posted in seamonkey. Bookmark the permalink.

20 Responses to SeaMonkey 2.39 is out

  1. ewong says:

    One would think that after doing SO MANY releases… I’d have the whole process down. But Nooooo. In my stupid haste of releasing the patch, I had made another mistake. 🙁 I pushed the release… and posted the above blog post. I was editing my post to the newsgroup when I suddenly realized (while editing the url to the release) that I had forgotten the website update. So… I had updated after I released. Way to go… ;/

  2. Sanny says:

    Thank you for this update.

    However, I am not going to update to any newer version, because I don’t see proper release notes, and the known issues seems to just be copied from previous releases.

    The last version that had proper release notes was 2.33, and although I commneted on the fact in previous posts, this seems to be the new state of things.

    With the direction Mozilla takes recently, one cannot trust blindly into new versions anymore.

  3. Were there any bug-fixes between 2.39b1 and 2.39?

  4. James LaBarre says:

    What has gone wrong with Seamonkey recently? On both of my brother’s MSWin machines, SM is SEVERELY slow and unresponsive. One is running MSWin7, the other MSWin8.1, both updated to latest fixpacks (excluding the MSWin10 nagware, which I have blocked on both).

    He’s had a lot of sites that take forever to load, or do not load at all. Sometimes opening a page will cause the browser to lock up, forcing him to kill the process in Task Manager. The same sites work acceptably in Firefox. Up until recently it had been the other way around, with SM far outperforming FF.

    Just now had been trying to look at saved passwords. The “data manager” screen shows the Cookies tab, and it will NOT switch off of that tab (clicking on the Passwords tab does absolutely nothing). This is SM 2.39 (just updated, 2.38 was doing the same exact non-response).

  5. George says:

    Thanks guys for the update! Also appreciate the blog and latest news! 🙂 !

  6. belphegore says:

    Where can I download still Seamonkey 2.37?
    I have still problems with the password auto fill, workaround for 2.38 is not working and 2.39 has the same issue…

  7. Rick K. says:

    I tried downloading it, but my antivirus flagged Trojan: Win32/Varpes.J!plock as imbedded, no matter who I tried downloading the browser from. I suggest you look into this.

  8. Reziac says:

    Why does the password manager no longer include passwords that are used in the email client? This is a critical deficiency. 🙁

Leave a Reply to Rainer Bielefeld Cancel reply

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