+1! I really think we need more testing and less bugs! I hope I can assist in QA and testing new releases in the future. Am 31.10.2013 13:54, schrieb Sandro Bonazzola:

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?

-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

Hi Sandro, On 10/31/2013 01:54 PM, Sandro Bonazzola wrote:

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?

I think it's an awesome idea! I imagine the main activities of the group will be testing nightly builds, reporting test failures to the appropriate places, and co-ordinating test days for oVirt? While the group is finding its feet I would encourage you to start with a wiki page listing the people committed to helping, and use the Users list to keep activity here. Use a special QE tag in the subject ([qe], perhaps) but stay here until there is sufficient activity to spin off a separate mailing list. Otherwise, I fear that the group will have trouble taking off, and will not get the community attention & participation it deserves. What do you think? -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

----- Original Message -----

From: "Sandro Bonazzola" <sbonazzo@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