if rules are set up for a process like this one, following these rules is a major benefit in itself - even if you personally don't agree with these rules. not only does it guarantee a standard quality; it also shows if the rules work or not. ignoring the rules won't make them better.

as for the current rules and the bugtracker issue:
i think the current QA rules are reasonable. you might be tempted to argue if the lack of a valid bug tracker really should be a blocker.... yes, i think it should be. either the project does have a tracker; then it's so easy for the author to include it that he ha no excuse at all not to do it. or the project really doesn't have a tracker - well, then it mustn't be released in extras. you cannot just release software without letting ppl know how to report bugs.

so i don't really see the benefit if dropping this requirement. i also don't see why testers should kind of "silently ignore" the fact that it's missing, hoping that a tracker will be added in the next release or the one afterwards. if the author doesn't do it when he first gets his package in testing, he most likely never will.

there's a very clear documentation that says which criteria have to be met for a package to be promoted to extras. if these criteria aren't met, authors shouldn't try to push their work into -testing in the first place. and testerst shouldn't vote those pakages up based on nothing else than "cool application, works great!". that's not enough.

all in all it comes down to:

• A clear set of testing requirements and rules.
• A clear set of todo's for a developer (I'm still trying to figure out how to create a bugtracker!! Wiki is a mare!!!)

Then after that actually getting both sides to follow it - only way to do that is to monitor it - oh the joys

I reviewed the wiki again and am confused what the problem is.
It doesn't say that bugzilla has to be used, just that it's recommended. The point is to provide some location for bugs to be reported.

Let's not get confused on this point. Mikko's app seems to me to meet this criterion.

a comment from QA on one of the packages....

"
Bugtracker link is not required in package data. Bugtracker must exist and it can be indicated otherwise too. Using XSBC-Bugtracker link is not always good idea because it's too hard to change it (requires new version of a package). http://maemo.org/downloads bug link can be changed manually when it's not included in package. http://maemo.org/downloads is the only place where the link actually matters."

this was in response to a QA that gave thumbs down for an app of mine not having a bug tracker link.
does make some sense, I agree the process in itself is not clear, and IMHO needs to be reviewed again. Giving thumbs down is not a solution.

I don't think anyone argued for dropping the requirement. The problem is twofold. One, that 'what constitutes a bugtracker' is interpretation prone. Two, that it is something that does not affect the package itself in any way, and yet a fix is expected to pass the same 10 day quarantine, QA procedure and 10 vote-ups as a full release.

Not having a bugtracker is unacceptable, but It is just as unacceptable (I'd even say even more) to delay an app for a month or so because the rules are unclear about a single http/mail link.

hmmm how about in my case... i have a broken bugrtracker link that doesnt want to fix itself at all... but i have put the Talk thread link in the description (here - http://maemo.org/packages/package_in...check/0.5.2-3/ )

Your debian/control contains a duplicate "XSBC-Bugtracker: " string:

Change it to

instead.

Ahhh but if i change it, it resets the testing phase... as the detail name of the package contains a link as well, i'd assume it should be fine? (Obviously personal interest in this matter seems to differ though)....

I'd say put up a fixed version - it's only half a day lost, and I'm sure you'll get the votes well before the 10-day quarantine ends.

True, meh, need to do it at home when i get time - may not until the weekend - (Although my recent thread spamming means i might hehehe)

It will reset the votes and time though i think - woulda been nice to get that up and going while i work on the other issues instead.