Update testing policy: how to use Bodhi

[Björn Persson]

Till Maas wrote:
> Even
> if an update is there to fix something, it does not mean that one can or
> will test it completely (special hardware might be required). In this
> case it is still interesting to know, whether it installs cleanly or
> not. And testing whether it updates cleanly can still be done
> intentionally, even when the package is not used. Just taking a look at
> the output of "yum --enablerepo=*-testing update" is enough for this.

I thought the plan was to have AutoQA verify that packages install cleanly. 
Isn't it better to automate such simple checks and save human resources for 
the things that can't be automated? Or do you think even just installing 
updates is too complex to be tested automatically?

Björn Persson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20100331/a667dd30/attachment.bin