(Not sure it belongs to the Mageia or the Infrastructure product - it's more about continuous QA) The situation is this: at each release, we get to make sure the upgrade process from release N to N+1 (at least) works smoothly (see https://wiki.mageia.org/en/QA_process_for_testing_upgrades). Not all, but several, if not most, of these tests can be automated. * have a set of standard VMs of Mageia N (today, 1 and 2) * every (day|week), a script: * upgrades a copy of those images to Cauldron * checks that resulting systems are not broken * adds to a report, and if needed, sends a warning to packagers This of course has a limited coverage at first: it's in a virtualized environment and at the beginning, at least, won't test much, but that the system is working at a minimum. That still helps to make sure a minimum is auto-tested. With a continuous check and detection of upgrade breakage, this can help the QA team focus on not-yet-scriptable tests.
http://mageia.madb.org/package/comparison/release/1/withrelease/2/application/0/source/1/comptype/older
CC: (none) => marja11, qa-bugs
(In reply to Manuel Hiebel from comment #1) > http://mageia.madb.org/package/comparison/release/1/withrelease/2/ > application/0/source/1/comptype/older and now: http://madb.mageia.org/package/comparison/release/5/withrelease/cauldron/application/0/source/1/comptype/older Anyway, assigning this request for auto-upgrade-testing to sysadmin team, because they're the only ones who are capable of doing this (of course, when there's enough time, enough server space, and nothing more urgent).
Hardware: i586 => AllAssignee: bugsquad => sysadmin-bugs