On Tue, 15 Nov 2011 01:40:13 -0500, Michael Scherer <[email protected]> wrote:
Or do we plan to do "it started, so it is good enough, let's ship it" ?
QA policy is to try and recreate the bug, if possible, in order to confirm that the update fixes the bug it claims to fix. We also test that the primary functions of the package works. For example, in an update for unetbootin https://bugs.mageia.org/show_bug.cgi?id=1443 the update did what it stated it would do, by invoking consolehelper, but the package didn't work. It wasn't a regression, but as the packages main feature didn't work, the update was not accepted until it was fixed. Every update is treated on a case by case basis, as to what testing will be done, taking into account things such as the impact it will have on inexperienced users if a problem does get pushed to updates. Something like a game, will get minimal testing. Something like packagekit-command-not-found, which could seriously break a system will get extensive testing, and will be blocked until it is safe to use. Regards, Dave Hodgins
