As it happens, I made a Brainstorm this morning about this issue. I had no idea that this was already been discussed. But RevdKathy kindly pointed me to this thread. As my defence, Talk was down when I did it, so I could not search the forum.

Anyway, since this is been discussed, let me offer my opinion too. These are the issues I have with the current system (and some of them have already been mentioned):

1. A new version in Extras-testing resets package Karma/quarantine time

For example, I got this app in Extras-testing. I know that there is a little mistake on the actual help file. It say "time you want to countdown from" instead of "count up from". Normally I would just correct this in few minutes. But with the current system I would loose the Karma/quarantine time of the app. I already lost them once, so I'm not going to do that again. Granted, it won't affect the functionality of the app, but it might confuse some end-users. However, I still think that the user would much rather have it sooner instead of having a grammatically correct help file 10 days later (that is, if it would get so many votes, which is highly unlikely, so the real wait might be several weeks. In other words, this current system discourages updates!

2. Why can't bug reporting page be automated?

The preferred place for bug reporting is Bugzilla. Fine. I have nothing against that. However, with the current method, I have to fist release my package, send an email to request a Bugzilla page for my package, wait for the creation of that page and finally release another package with the correct reference to the Bugzilla page. Why could there not be a simple way to auto create the proper Bugzilla place, like the Optify - Auto setting? If some additional pages or settings are needed, only then could a request be sent.

3. There are no testers in Extras-devel

A developer needs testers. But those are not available in Extras-devel. Especially since the user is warned that his device will explode if he activates this repository filled with malicious apps from mad developers who are secretly palning to take over the world. So the only real testing can happen in Extras-testing. Therefore there should be two stages:

Beta testing

A stage where the developer can get valuable feedback from users and thus improve the app. Updates that add features are allowed.

Release candidate

A stage that is initiated by the developer himself. Yes, not all developers are clinically insane megalomaniacs! Some of them actually take bride of the quality of their work and don't want to release a product that is not working well. In this stage, only bug fixing and some minor needed functionality changes would be allowed.

For these two stages, there should be some kind of unified voting system. What system? I have no idea and I'm tired of typing.

Anyway, this was only my opinion. Not that great, I know, but at least it's mine.