On 09/01/06, Axel Hecht <[EMAIL PROTECTED]> wrote: > I'm not convinced that asking other volunteers to review an 0.0.0.2 > extension, expecting another version to come in in a week or two is the > appropriate way of dealing with those ressources.
I used to agree with this. In fact I still might. But as an extension developer who's not in the top five, my releases fall into two categories - major functionality changes - EQF's to deal with problems in the above changes It would be nice, and probably more responsible of me, to release alpha's and beta's of major changes, and that was my original intention. Turns out that doesn't fit my work when the kids are asleep development cycle. Also with only a few thousand users I don't currently have enough volunteer beta testers to avoid some pretty embarrassing bugs, especially considering I'm a professional software developer. Though on the other hand my understanding is that UMO reviews aren't QA. Rather they only cover a few things: - make sure that the extension comes up, kind of does something, and doesn't immediately crash the browser - isn't a key logger etc. - doesn't compromise the browser some other way e.g. by downloading itself or other code from somewhere else I'd like to think that after the initial review, using diff tools the review itself shouldn't be more than 10 or 15 minutes. Also I think having a link to the homepage in the extension's menu is enough to satisfy the users who want/need more frequent updates. I thought I had a conclusion, but I've lost track of it... A _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
