Updates Criteria Summary/Brainstorming

[Mike Fedyk]

On Mon, Nov 22, 2010 at 7:01 AM, Kevin Kofler <kevin.kofler at chello.at> wrote:
> Michal Hlavinka wrote:
>> this could help, but it's not always possible to add these test cases. One
>> example: imap server package - new bug that can corrupt mail folders in
>> some circumstances. Maintainer updates package and sets 'type=bugfix' in
>> bodhi, but not always it's possible to write down any test case. It's
>> still a bug fix and it's better to be delivered sooner than wait if anyone
>> out there get's his mail folders corrupted. Actual policy does not help
>> proactivity.
>
> Right, and the big point there should be that a bug which can corrupt mail
> folders should be fixed IMMEDIATELY, i.e. with a direct stable push! ANY
> testing requirement there is a failure.
>

Install package from updates-testing, then +1 to karma after it works
for you with your tests and normal workload.

Simple.

No need to foist possibly broken software on everyone.