SeaMonkey/Tasks & Projects/Add-on compatibility

From MozillaWiki
< SeaMonkey
Revision as of 09:24, 27 July 2015 by Rrbd (talk | contribs) (Formatting)
Jump to navigation Jump to search
SeaMonkeylogo.png
Task.png
Tasks & Projects
SeaMonkey Homepage
AMO Browsing for SeaMonkey - Localization
SeaMonkey Sync
Add-on compatibility tests
Ideas for a new debugQA-add-on
IRC Chat Logs

The Problem

"Add-on Compatibility Reporter" add-on still does not work and the wiki page <https://wiki.mozilla.org/SeaMonkey/AddonCompat> costs too much work, os we need a alternative approach to gain user experience

The Plan

(Experimental)
An experimental thread "Add-on Compat SM 2.35 - " at Newsgroup mozilla.support.seamonkey

How to use

SM 2.35 addon-compat –

Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [yes] – WINDOWS
Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [no] – MAC
Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [no] – LINUX
Body: After add-on-install: SM <… complete user agent string> CRASH immediately after launch
Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [yes] – WINDOWS
Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [yes] – MAC
Re: SM 2.35 addon-compat – DownThemAll! 2.0.18.1-signed – [yes] – LINUX

Some Details

  1. Always answer to an existing sub thread concerning an add-on
  2. Add user agent string in posting body, if yo have a "no" in subject please add a precise problem description corresponding to Bug Writing Guidelines so that add-on author can use your description for a fix
  3. Use [yes] if add-on was compatible during your tests
  4. Use [no] if add-on was NOT compatible during your tests
  5. Use [yesconvert] if converted add-on was compatible during your tests
  6. Use [noconvert] if converted add-on was NOT compatible during your tests
  7. If you have Information concerning compatibility with an add-on doe a new SeaMonkey Version without thread please start a new thread like "SM 2.39 addon-compat –" and then answer with your information
  8. Do not start threads for smaller bugfix releases like 2.33.2 or similar