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.
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… ;/
Ha. I was wondering why http://www.seamonkey-project.org/releases/seamonkey2.39/ mentions Beta 1. :/
It happens. 🙁
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.
You can find some more recent additional Release Notes in the German Blog.
With fixes for
1222825: Tracking bug: Rework SeaMonkey Release Notes 2.39 / 2.40
1203402: Remove Known Issue: Linux Cursor Change Hang
1206519: SeaMonkey 2.38 Release Notes: Mention Add-on-Converter …
1209859: SeaMonkey 2.38 Release Notes: Rework “Known Issues – Bug 521861”
1222826: Add current known Issues to 2.39 Release Notes
1222827: Add “Fixed bugs” to SM 2.39 Release Notes
1222883: Release Notes: remove WFM known issue “Bug 622410 – Vertical scrolling with trackpointBug 622410 – Vertical scrolling with trackpoint …”
we will get current release notes also at SeaMonkey-Project.org
I am tired with this “Your comment is awaiting moderation” bother.
Thanks for the effort Rainer.
However, all I can understand from this reply (and the post on SeaMonkey 2.39 additional Release Notes) is that there were several bug reports about the release notes issues I mentioned above, and some reference to unknown previous issues from v2.38.
The only actual fixes I can see are 2 Linux-related issues with cursor and scroll.
I can’t believe that is all what v2.39 is about.
What about core changes?
Any new functions added to this version?
Any removed functions?
Any new files on the profile folder or configuration strings?
If so, what do each mean?
These are not questions.
I would like these topics to be clearly listed in each release notes, so we, the users, can decide how to proceed.
Again, thanks for your efforts.
Of course the completeness of current release notes is not satisfying. But to check those 391 new FF/TB/Core bugs (for example) and the 717 fixed bugs for SeaMonkey-relevancy would be a lot of work, for what we do not have enough volunteers. Additionally that would need some infrastructure, but I will not invest time to create infrastructure if I do not know that there are volunteers to help.
Do you think you can help a little? It’s not only work, but also fun and a possibility to learn a lot about SeaMonkey.
But one additional problem might be: all that testing of Core-bugs will not at all accelerate the bug fixing process, most of the work would only be for better release notes. Is it that worth? But at least, of course, these existing obstacles should not be a excuse to adjourn improvement of the release notes (see Bug 1222825)
Please send me contact info to sanny at discardmail dot de, so we can continue offline.
Were there any bug-fixes between 2.39b1 and 2.39?
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).
Does this happen in a new profile?
This is not the appropriate place for bug reports. Please:
Read Bug writing guidelines
Report a bug concerning your problems in Bugzilla (after having created a Bugzilla Account if necessary)
Thanks guys for the update! Also appreciate the blog and latest news! 🙂 !
Don’t forget releases from Adrian Kalla …
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…
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.
Where are you downloading it from? Also, which anti-virus?
Why does the password manager no longer include passwords that are used in the email client? This is a critical deficiency. 🙁