Apart from the earlier comments about difficulties in getting any app stabilised enough, I think there are three things necessary:

1. Clearer communication on what's required from app authors (there's a process doc which is the output of the earlier task. Not directly suitable for package maintainers.
2. Technology in place (maemian etc.) to do some basic automated checks (big warnings which have to be specifically overruled for any lib* package in section: user/..., for example)
3. Instructions for how to promote when you want to.

The last point is particularly important: I just went to my package and couldn't see a "Promote" button anywhere; despite looking.

Of course, with a bit of thought, it's obvious I have to promote an individual version - but then I have to promote the armel & x86 versions separately: a step back from the earlier extras-devel -> extras promotion interface, IMHO.

I think it's likely a developer will want to promote all the architectures, and OS versions, for the latest version of a package. Perhaps some kind of checkbox & promote button on a package; or a "Promote latest" button would help?

Ultimately, this is a question for Niels - he knows whether the software's stable and ready for more testing yet.