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).