126
edits
AMO:Authors: Difference between revisions
m
→How to Get Your Addon Reviewed Faster: - Spelling errors, linked mozillazine forums
m (→How to Get Your Addon Reviewed Faster: - Spelling errors, linked mozillazine forums) |
|||
| Line 18: | Line 18: | ||
=== How to Get Your Addon Reviewed Faster === | === How to Get Your Addon Reviewed Faster === | ||
The popularity of Firefox and addons has lead to a significant increase in the number of addons submitted to UMO for review, and with only a small number of active reviewers, the number of addons in the queue on average is increasing. There are a few ways in which you can speed up this process and make it easier for us, and therefore, faster for you. | The popularity of Firefox and addons has lead to a significant increase in the number of addons submitted to UMO for review, and with only a small number of active reviewers, the number of addons in the queue on average is increasing. There are a few ways in which you can speed up this process and make it easier for us, and therefore, faster for you. | ||
* Comply with [[Update:Requirements/LegalAndReview|these policies]]. They're only drafts at the moment, but we still enforce them. The most common one people fail on is that your addon must not specify an UpdateUrl. UMO will | * Comply with [[Update:Requirements/LegalAndReview|these policies]]. They're only drafts at the moment, but we still enforce them. The most common one people fail on is that your addon must not specify an UpdateUrl. UMO will automatically offer updates to your addon to users when you submit new versions of your addon and we have reviewed them. | ||
* Do not use the UMO reviewers as beta testers and bug finders. This is not the purpose of reviewers. Please test the addon extensively before submitting. | * Do not use the UMO reviewers as beta testers and bug finders. This is not the purpose of reviewers. Please test the addon extensively before submitting. | ||
* If possible, have a public system on your website for reporting and managing bugs in your addon. This is an invaluable resource for us when we are reviewing your addon as it gives us information on any problems in your addon. | * If possible, have a public system on your website for reporting and managing bugs in your addon. This is an invaluable resource for us when we are reviewing your addon as it gives us information on any problems in your addon. | ||
* If possible, conduct a beta release cycle from your website every time you want to release a new version of your addon. Allow your current users to be involved, but be sure to warn them that the addon is in beta ;) Conducting a beta cycle will ensure your addon has less bugs and is of a higher quality when you release it and/or release new versions. | * If possible, conduct a beta release cycle from your website every time you want to release a new version of your addon. Allow your current users to be involved, but be sure to warn them that the addon is in beta ;) Conducting a beta cycle will ensure your addon has less bugs and is of a higher quality when you release it and/or release new versions. | ||
* If possible, have a public forum on your website for users to critique, comment on and discuss your addon. If this is not possible or | * If possible, have a public forum on your website for users to critique, comment on and discuss your addon. If this is not possible or impractical, create a topic on the [http://forums.mozillazine.org/viewforum.php?f=19 Mozillazine Extension forum] about your addon - this will group together any comments that users have about your addon and allow reviewers to gather information about your addon more speedily. | ||
* If you are updating your addon, have a changelog on your website. This will inform us what parts of the | * If you are updating your addon, have a changelog on your website. This will inform us what parts of the addon have changed and which parts we especially need to test and give extra scrutiny to. | ||
* This is mentioned above, but it's important so I'll mention it again. Only declare compatibility with application versions and operating systems that you have tested with. If version 2.3 of your addon worked with Firefox 1.0.* and you're planning on releasing 2.4 which is compatible with Firefox 1.5.0.*, you should ONLY declare compatibility with Firefox 1.5.0.*, unless you have tested your addon with 1.0.*, in which case you should declare compatibility with both. | * This is mentioned above, but it's important so I'll mention it again. Only declare compatibility with application versions and operating systems that you have tested with. If version 2.3 of your addon worked with Firefox 1.0.* and you're planning on releasing 2.4 which is compatible with Firefox 1.5.0.*, you should ONLY declare compatibility with Firefox 1.5.0.*, unless you have tested your addon with 1.0.*, in which case you should declare compatibility with both. Don't simply assume that because your addon works in Firefox that it will work in Flock, or that because it works in Thunderbird that it'll work in Mozilla - you need to test this extensively. | ||
== Welcome Page == | == Welcome Page == | ||