I think I can recommend that Beta version, I have been using 2.53 for a long time without bigger problems. But you should keep in mind that there will be no way back for your existing User Profile after you will have used it with 2.53.
You should do a backup of your User Profile before you launch the new build firrst time.
Download and more information: SeaMonkey 2.53.3 Beta 1
User wg9s offers several current SeaMonkey builds from latest source for WINDOWS, MAC and Linux.
SeaMonkey 2.53.4 is the new successor of 2.53.3, German version works fine for me on WIN, English Version and other OS not (yet) Tested by me.
Reports on Expereience are welcome, but please be aware that you use those builds on your own risk. I recommend to create a backup of your user profile before you start testing those builds.
I started to test 2.53.1 today, until now it works fine for me.
Hello,
it’s not a secret that SeaMonkey-development is understaffed. At the right you see 2 statistic charts:
Totally 20 bugfixes / month, that is much better than (for example) at the AOo project with only 5 bugfixes each month, but much worse than in the LibreOffice project with: 545 bugfixes within 1/4 year — and see the colorful “pie“. Of course a pointless comparison, but it demonstrates the critical situation for the SeaMonkey project with very few developers.
But may be there are people with basic (or even good) bug fixing skills, who only shied from the many obstacles before they can start? Some of them can be surmounted easil:
But the next steps are much more difficult:
I think interested volunteers should fix a weekend with some kind of time table where they do these first steps together, help each other, might even get help of a mentor form the SeaMonkey Developers Team … .
May be we even can get some external volunteers from Hackerearth, CodeChef, TopCoder,Codeforces,HackerRank or similar communities (may be you know a better community were we can try to recruit volunteers?)? Or, if we are lucky, some “self compiling users” are willing to provide their knowledge to the SeaMonkey project?
If you have some own thoughts, please add a comment as reply to one of the threads:
One of my favorite add-ons crashes latest SeaMonkey Trunk-Builds like
UNofficial (by FRG) en-US SeaMonkey 2.52a1 (NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 Build 20170513191754 (Default Classic Theme) on German WIN7 64bit
When I launch SeaMonkey it crashes immediately if PrefBar add-on is active.
The problem is not Win64; x64 related.
Bugs:
Can someone confirm the problem❔
Any theory concerning the roots of the problem❔
The SeaMonkey project is entirely driven by volunteers, and we will need some more of them, as FRG (Frank-Rainer Grahl) told on mozillazine.
With some HTML and XHTML knowledge (and some endurance, of course) for example you can do substantial contribution to SeaMonkey Help. Also required: Translation to other languages than English for Help-chapters, Add-Ons, Wiki-pages…
Don’t be shy, leave a comment how we can reach you and where you see your skills for contribution.
Based on postings in de.comm.software.mozilla.mailnews (“[SM 2.46] Leerzeilen verschwinden beim Antworten”) I reported Bug 1329724 – Empty lines in email body disappear, but until now it seems nobody was able to reproduce the problem with the steps from bug report.
I did tests on mozilla.test with Server-Installations of unofficial (by FRG) en-US SeaMonkey 2.50a1 (NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 Build 20170108183322 (Default Classic Theme) on German WIN7 64bit (Re: Empty lines disappear, Rainer Bielefeld 06:08 +0100, Message-ID: <V8OdnYbIGKeq8enFnZ2dnUU7-cOdnZ2d@mozilla.org>, and the issue was still reproducible.
It would be great if someone else could reproduce the problem with the Steps To Reproduce from my report.
And, of course, it also would be great if you find other reliable ways how to provoke disappearing empty lines in replies; please submit additional separate Bugs if you are not sure that the problem you observe is exactly the same.
Adrian Kalla again contributed lots of unofficial English and localized installers and language packs in various languages for WINDOWS and Linux:
Dates for the folders are wrong. In fact folder contents is 2016-10-26, 2016-10-27
| latest-comm-central-linux32/ | 2016-09-23 |
| latest-comm-central-linux64/ | 2016-09-23 |
| latest-comm-central-windows32/ | 2016-09-24 |
| latest-comm-central-windows64/ | 2016-09-24 |
Additional builds with date 2016-10-16 / 2016-10-17 available:
With today’s WINDOWS build I observed the Problems described in Bug 1300530 – “Edit As New” opens broken HTML Composition Window with missing contents, possibly add-on-related. and others. It would be great if some of you could help to narrow down the roots of the problem.
After a while of waiting we now have new SeaMonkey Trunk builds for MAC
Be careful! These builds are for testing purposes only. Keep backups of your data, some of the code you’re testing might not have been tested at all before and might cause unexpected problems. If you encounter any such problems, please report bugs for them.
I still report new bugs I find with status UNCONFIRMED, even if (after careful investigation) I am pretty sure that the report is concerning a real bug and complete enough so that a developer can take on. Reason is that I believe in the two-man rule. Often a review by an other user adds information, may be concerning additionally affected Operating System or an aspect of the problem not yet mentioned or something else. But in the SeaMonkey project, due to very limit “human QA resources” and the lack of interest of most SeaMonkey users to contribute to the project, the bug review process is horrible slow, even Bug reports what can be reproduced easily do not find a user who is willing to do a test whether he can reproduce the problem.
SeaMonkey needs you
So in future I myself will change bug status to NEW after 2 weeks (or so) of waiting if I think that all requirements for starting bug fixing process are fulfilled and nobody confirmed the bug. But, of course, it would be great if YOUR help would make superfluous this proceeding with my own “confirmation”. Be courageous and grasp the nettle of confirming some [easyconfirm] bugs.
SeaMonkey Internet Suite 