[Project_owners] Awaiting extension upgrade approval
Onno Ekker
o.e.ekker at gmail.com
Mon Jul 7 23:13:17 PDT 2008
On Tue, Jul 8, 2008 at 4:29 AM, Michael Vincent van Rantwijk, MultiZilla <
mv_van_rantwijk at yahoo.com> wrote:
> AMO isn't an absolute necessity to release new versions of your software.
> Surely you must know that by now, especially since you post here ;)
>
You don't need AMO, but it helps greatly getting your extention to end
users. I have a small Thunderbird extension and had about 2 downloads a day
on mozdev, 5 on AMO before going public and now 30...
Most end users on AMO won't go looking for an update on your project
website. They won't even realize there might be a newer version there, or in
the sandbox.
I would however like to advise you to open your favorite IRC proggy and go
> beg for support (insert you devils smiley here). Now seriously, this has
> got to change a.s.a.p. I agree. And totally!
Project owners could have helped to take the strain from editors too, by not
waiting for the next major release to update their add-on, but starting with
it as soon as the first alpha was released (or even before that). Once an
extension is compatible (and reviewed), you only need to bump maxVersion if
it stays compatible and no further reviewing is necessary for that. Some
project owners probably have done that, but others have waited too long and
now suffer the consequences of that.
If you don't like the way AMO/reviewing is working, it might be an idea to
file a bug for it. Or vote for one, if you can find an existing one. But
(all/most?) reviewers are volunteers, just like you and me, and they do
their best to review each add-on.
Onno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mozdev.org/pipermail/project_owners/attachments/20080708/98ef9855/attachment.html>
More information about the Project_owners
mailing list