Unfortunately our supporters list in the wiki has become very outdated and useless, because most of the listed persons no longer do support SeaMonkey.
So I decided to rework that list, goal is to have a reliable overview what persons actively do support SeaMonkey and are available for questions of other users, support to SeaMonkey tasks and similar.
For former supporters who have left the SeaMonkey project I created a new page.
As preparation I wrote an e-mail to all persons listed in the old supporters table. My result:
- 44 Wrong e-mail-addresses
- 03 users who asked me to remove them from the table
- 01 Users Who told me that he is still active
- 02 Users who told me that they still are interested in contributing, but currently hibernating
- 05 personal e-mails with various other contents
- 108 e-mails without any automated or personal reaction
I expect that users, who received an e-mail but did not answer, are not interested in any contact or activity, so I removed them from the table. The result is a very short stub of an accurate supporters list.
Of course I know that this new list is incomplete, I do not know all supporters and did not yet find enough time for further research. So please add yourself to the list if you are active in the SeaMonkey project, if you agree that other supporters will address you and if and your name is missing in the new list. If your name has been deleted from the old table you can simply copy / paste the text line with the table row for your name from an older Version of the wiki page. If you do not have a Wiki-account and do not want to create one for that single action please simply leave a comment here with required information, someone will add it to the table.
And of course, please update your entry and correct errors, any help to get a more useful “contact-brokering service” in the wiki is appreciated.
In the following some additional release information what currently still are missing at the official SeaMonkey release notes.
Here you find a Google machine translation of the official SeaMonkey Website for approximately 90 languages. The result sometimes isn’t easy to understand, but may be better than nothing – alternatively you can try regional websites.
Here are some queries what might be useful for the decision whether to update to 2.35 or not (without any guarantee of completeness and correctness):
A Bugzilla account and also to be logged in to Bugzilla is required to do the queries and to see the list
Please consider that the queries do not contain any bugs that exist (or have been repaired) in Firefox or Thunderbird without having been reported for SeaMonkey separately in Bugzilla. On occasion I will try to find more useful queries.
The queries are dynamic and take into account progress (and setbacks) immediately.
Some new SeaMonkey 2.35 features are listed in the Wiki.
Unfortunately for the latest SeaMonkey 2.35 version with several security patches no language packs were available. Because my experience is that the 2.35 language packs Adrian Kalla contributed some weeks ago (and what are no longer available at his download area) work fine with that latest 2.35 build I asked him to send those language builds to me, and I made them available for public download at sourceforge.net.
On that page Adrian Kalla contributes localized installers.exe and languagepacks.xpi in various languages.
Only for testing, you will use those builds on your own risk.
This build (by Philip Chee) includes the latest security fixes like Mozilla Foundation Security Advisory 2015-78. SeaMonkey and Thunderbird do not ship the Firefox integrated PDF reader so we are not affected by this. However there are other security and crash fixes so do please help test these latest builds.
here you can read why I started a new attempt at Newsgroup mozilla.addons.user-experience (on news server news.mozilla.org to get something like an add-on compatibility data base with the help of the SeaMonkey users community.
On the same Wiki page you also will find some “how to use” hints.
I hope I won’t be the only contributer again ;-.)
We have something very similar to a Release Candidate, “all-bugfixes included“, but not localized.
That version contains a lot of bug-fixes compared to SeaMonkey 2.33 (no warranty for completeness) , intensive testing is appreciated.
Be careful with Language Packs (and may be other add-ons) for 2.33, they might cause big problems with 2.35, and currently I do not know whether fix for Bug 1084258 – Language pack compatibility should be bound to Gecko branch, else undefined entity errors possible already will avoid such problems.
Backup your profile before you install and test!
Linux Users: please consider Bug 1057581 – old profile crashes on startup [@ nsRDFPropertyTestNode::FilterInstantiations]
On the same download page you will find an Aurora 2.38a1 build.
On mozilla.support.seamonkey Ed Mullen asked 2015-07-07 the question from heading. I tried to ask Bugzilla for an answer by comparing some activity parameters with numbers of year before and 5 years ago (2010). All values for first half-year. Found numbers are listed in table below, queries for 2015 are linked in the left column:
I think new reports and changed to FIXED (bug fixes) no not need explication. The next parameters are indicators for (user-) QA activity. The table shows that 2015 we have only half as much activity left as SeaMonkey had 2010. But compared to year before it even looks some better.
And we have some additional glimmers of hope:
Of course that’s not a substitution for security patches coming in time, and we still have the Sync problem (and others).
But be aware: it depends on you and your contribution how successful SeaMonkey can be. You think a normal user can’t help? That’s not true, as a first step you can try to confirm (or disprove) some of our UNCONFIRMED SeaMonkey bug Reports, like I do here (you may add me to CC if your are not sure whether your investigations are exhaustive). I hope to find your signature in Bugzilla, soon … . 🙂
- Built of mozilla-esr38 + THUNDERBIRD_38_VERBRANCH. Note Official 2.35 release will be built off mozilla-release 38 (Probably 38.0.6)
- DOM Inspector built off changeset 80c195824f1e. Version shows as 2.0.16pre. I have uploaded 2.0.16 to AMO so SeaMonkey should update to that version if configured.
- Chatzilla built off changeset c65366e47dd2. Version shows as 0.9.91.1 . This is a problem because SeaMonkey may update to the version on AMO (0.9.91.1.1-signed).
News from the machinery compartment
I am happy that we now have the blog. After some weeks experience with it, we should think about some improvements. Most of the following suggestions are also discussed in Bug 1147825 – (meta) Revive SeaMonkey blog and accomplished in the Inofficial German Language SeaMonkey Blog.