----- Original Message ----- > From: "Sandro Bonazzola" <sbona...@redhat.com> > To: "users" <users@ovirt.org> > Sent: Thursday, October 31, 2013 5:54:51 AM > Subject: [Users] oVirt quality team proposal > > Hi, > I would like to propose to the community to join creating a group for testing > oVirt > releases and oVirt bug fixes. I suggest to create a ovirt-qe mailing list and > set > that as default QE assignee for oVirt bugs. > The list may be used for coordinating testing efforts, to be notified about > new ovirt bugs, > to plan test days, propose test cases, discussing about jenkins jobs > implementation and so on. > Forming just a small group of people testing milestones release will also > help in having better release testing. > What do you think about this? >
+1 I'd be into it. I've been daydreaming about all sorts of automated tests: * oVirt stable + fedora updates * oVirt stable + fedora updates testing * oVirt nightly * oVirt nightly + fedora updates testing * etc. The quickstart case -- an AIO install -- should *always* work. If a user gives oVirt a shot once and gets hung up on some little issue, who knows if they'll ever try again? Jason > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users