Don't put new packages through updates-testing

[Luke Macken]

On Fri, Jun 01, 2007 at 04:55:29PM +0200, Hans de Goede wrote:
>  Will Woods wrote:
> > Let's be a little more clear here - what the QA team actually does for
> > packages in updates-testing is *verification*. Check package sanity,
> > make sure programs don't segfault on startup, etc. I'm not expecting all 
> > testers to understand the functions of the
> > packages as well as their maintainers. But anyone can tell if you missed
> > some deps or your package doesn't start on x86_64.
> 
>  1) I already verify my packages on x86_64 myself

That's great.  I don't.

>  2) starting libs is kinda hard

Agreed.  Matthias Clasen mentioned on fedora-maintainers how the
RHEL errata tool has a field where the engineer is supposed to
fill in QA test instructions, which might be a very useful thing for
bodhi to have.

>  3) Most missing deps are subtile and do not necesarry show when just running 
>  an
>     app
> 
>  It would be more usefull to check build-logs for things like:
>  -suspicious ./configure failures (due to missing BuildRequires)
>  -64 bit suspecious compiler output like cast from different size integer to
>   pointer (this could actually be automated)

I just added a 'Build Logs' link to updates in bodhi.


luke