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.
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 ;-.)
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 … . 🙂
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.