Fwd: [Users] oVirt quality team proposal
Hi, it seems that the proposal has been welcomed in users list, so I'm forwarding this to devel and infra for approval. Maybe we can benefit of ovirt-qa list for 3.3.1 testing before releasing it next week. -------- Messaggio originale -------- Oggetto: [Users] oVirt quality team proposal Data: Thu, 31 Oct 2013 13:54:51 +0100 Mittente: Sandro Bonazzola <sbonazzo@redhat.com> A: users <users@ovirt.org> 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? -- 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
Hi Sandro, I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea? Thanks! Dave. On 10/31/2013 04:20 PM, Sandro Bonazzola wrote:
Hi, it seems that the proposal has been welcomed in users list, so I'm forwarding this to devel and infra for approval. Maybe we can benefit of ovirt-qa list for 3.3.1 testing before releasing it next week.
-------- Messaggio originale -------- Oggetto: [Users] oVirt quality team proposal Data: Thu, 31 Oct 2013 13:54:51 +0100 Mittente: Sandro Bonazzola <sbonazzo@redhat.com> A: users <users@ovirt.org>
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?
-- 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
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
Thanks! Dave.
On 10/31/2013 04:20 PM, Sandro Bonazzola wrote:
Hi, it seems that the proposal has been welcomed in users list, so I'm forwarding this to devel and infra for approval. Maybe we can benefit of ovirt-qa list for 3.3.1 testing before releasing it next week.
-------- Messaggio originale -------- Oggetto: [Users] oVirt quality team proposal Data: Thu, 31 Oct 2013 13:54:51 +0100 Mittente: Sandro Bonazzola <sbonazzo@redhat.com> A: users <users@ovirt.org>
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?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Thanks! Dave.
On 10/31/2013 04:20 PM, Sandro Bonazzola wrote:
Hi, it seems that the proposal has been welcomed in users list, so I'm forwarding this to devel and infra for approval. Maybe we can benefit of ovirt-qa list for 3.3.1 testing before releasing it next week.
-------- Messaggio originale -------- Oggetto: [Users] oVirt quality team proposal Data: Thu, 31 Oct 2013 13:54:51 +0100 Mittente: Sandro Bonazzola <sbonazzo@redhat.com> A: users <users@ovirt.org>
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?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7vXCCjfoMSXTjPPq8WSBjlthrwRCKGgXL Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather tha= n creating a new list - do you think that's a bad idea?
No it's fine for me. =20 In order to set QA contact to users@ovirt.org, we need a bugzilla user = with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla. One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ... - Karsten --=20 Karsten 'quaid' Wade http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --7vXCCjfoMSXTjPPq8WSBjlthrwRCKGgXL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFSepIm2ZIOBq0ODEERAmDQAKCSC190WRjINyd+weacOf5kYCv4owCfd0Mg LCNVoUJ5rd00haYlhAms1rs= =7Ux8 -----END PGP SIGNATURE----- --7vXCCjfoMSXTjPPq8WSBjlthrwRCKGgXL--
On 11/06/2013 09:01 PM, Karsten 'quaid' Wade wrote:
On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
Il 08/11/2013 09:24, Itamar Heim ha scritto:
On 11/06/2013 09:01 PM, Karsten 'quaid' Wade wrote:
On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
yes
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 08/11/2013 09:25, Sandro Bonazzola ha scritto:
Il 08/11/2013 09:24, Itamar Heim ha scritto:
On 11/06/2013 09:01 PM, Karsten 'quaid' Wade wrote:
On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
yes
or better, I would like to have it as default QA assignee
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 11/08/2013 10:26 AM, Sandro Bonazzola wrote:
Il 08/11/2013 09:25, Sandro Bonazzola ha scritto:
Il 08/11/2013 09:24, Itamar Heim ha scritto:
On 11/06/2013 09:01 PM, Karsten 'quaid' Wade wrote:
On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto: > Hi Sandro, > > I suggested keeping activity on users during bootstrapping rather than > creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
yes
or better, I would like to have it as default QA assignee
it doesn't matter if its the default QA assignee, or cc'd by default on all bugs for email sake.
On 11/08/2013 10:25 AM, Sandro Bonazzola wrote:
Il 08/11/2013 09:24, Itamar Heim ha scritto:
On 11/06/2013 09:01 PM, Karsten 'quaid' Wade wrote:
On 11/06/2013 05:55 AM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
yes
i'd rather not flood users@ovirt.org with all bugzilla activity, so for sure a new mailing list for "listening on bug activity". though reply-to should be either in bugzilla, or to users mailing list. I'll check if we can solve the password reset issue somehow. thanks, Itamar
Hi Sandro, did you get this sorted? Bugzilla admins should be able to do that for you. Dave. On 11/06/2013 02:55 PM, Sandro Bonazzola wrote:
Il 31/10/2013 17:13, Sandro Bonazzola ha scritto:
Il 31/10/2013 16:58, Dave Neary ha scritto:
Hi Sandro,
I suggested keeping activity on users during bootstrapping rather than creating a new list - do you think that's a bad idea?
No it's fine for me.
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Thanks! Dave.
On 10/31/2013 04:20 PM, Sandro Bonazzola wrote:
Hi, it seems that the proposal has been welcomed in users list, so I'm forwarding this to devel and infra for approval. Maybe we can benefit of ovirt-qa list for 3.3.1 testing before releasing it next week.
-------- Messaggio originale -------- Oggetto: [Users] oVirt quality team proposal Data: Thu, 31 Oct 2013 13:54:51 +0100 Mittente: Sandro Bonazzola <sbonazzo@redhat.com> A: users <users@ovirt.org>
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?
-- 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
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
In order to set QA contact to users@ovirt.org, we need a bugzilla user with that email address. Is it possible to create it?
Challenge there is that then anyone can subscribe to users@ovirt.org, issue a password reset request, and jump on the reset before anyone else does. I'm not sure if there is a good workaround within bugzilla.
One idea is to use e.g. users-bugs@ovirt.org as a new email address that oVirt Infra controls, subscribe that address to users@ovirt.org, and have a procmail rule that copies all inbound email to users-bugs@ to users@ ... except that has the same problem as above. Hmm ...
what's the purpose of that user? just getting all emails on all bug changes to the mailing list?
yes
i'd rather not flood users@ovirt.org with all bugzilla activity, so for sure a new mailing list for "listening on bug activity". though reply-to should be either in bugzilla, or to users mailing list.
I'll check if we can solve the password reset issue somehow.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now? Like I said, the important piece is to ensure that conversations around the quality team happen on users. Cheers, Dave. -- 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
On 11/19/2013 12:55 PM, Dave Neary wrote:
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now?
Like I said, the important piece is to ensure that conversations around the quality team happen on users.
but i don't think we need all bug correspondence there, so we could just start discussing relevant things on users, even if bugs aren't changed for default assignee.
Il 19/11/2013 12:19, Itamar Heim ha scritto:
On 11/19/2013 12:55 PM, Dave Neary wrote:
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now?
Like I said, the important piece is to ensure that conversations around the quality team happen on users.
but i don't think we need all bug correspondence there, so we could just start discussing relevant things on users, even if bugs aren't changed for default assignee.
I agree. I've already posted a few e-mails with [QE] in subject trying to gather interest in some bugs verification / scrubing. For the bug assignee, I think that the new list proposed by Itamar is the best solution. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 19/11/2013 12:19, Itamar Heim ha scritto:
On 11/19/2013 12:55 PM, Dave Neary wrote:
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now?
Like I said, the important piece is to ensure that conversations around the quality team happen on users.
but i don't think we need all bug correspondence there, so we could just start discussing relevant things on users, even if bugs aren't changed for default assignee.
The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list? After that, we can set it as QA default assignee at least for ovirt-engine packages. - ovirt-engine-core - ovirt-engine-installer - ovirt-engine-userportal - ovirt-engine-webadmin Others may follow later. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 21/11/2013 08:00, Sandro Bonazzola ha scritto:
Il 19/11/2013 12:19, Itamar Heim ha scritto:
On 11/19/2013 12:55 PM, Dave Neary wrote:
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now?
Like I said, the important piece is to ensure that conversations around the quality team happen on users.
but i don't think we need all bug correspondence there, so we could just start discussing relevant things on users, even if bugs aren't changed for default assignee.
The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list? After that, we can set it as QA default assignee at least for ovirt-engine packages.
- ovirt-engine-core - ovirt-engine-installer - ovirt-engine-userportal - ovirt-engine-webadmin
Others may follow later.
Talking with Itamar, this mailing list should not accept emails from anyone else and reject them automatically. replies should go to users@ovirt.org for discussion, as dneary suggested. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 21/11/2013 09:41, Sandro Bonazzola ha scritto:
Il 21/11/2013 08:00, Sandro Bonazzola ha scritto:
Il 19/11/2013 12:19, Itamar Heim ha scritto:
On 11/19/2013 12:55 PM, Dave Neary wrote:
On 11/18/2013 12:09 PM, Sandro Bonazzola wrote:
Il 18/11/2013 11:57, Dave Neary ha scritto:
Hi Sandro, did you get this sorted?
Bugzilla admins should be able to do that for you.
No. Last thread about this was (last reply from Itamar):
OK - noted. Thanks. What do you plan to do now?
Like I said, the important piece is to ensure that conversations around the quality team happen on users.
but i don't think we need all bug correspondence there, so we could just start discussing relevant things on users, even if bugs aren't changed for default assignee.
The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list?
I can't see ovirt-bugs@ovirt.org in http://lists.ovirt.org/mailman/listinfo . The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list?
After that, we can set it as QA default assignee at least for ovirt-engine packages.
- ovirt-engine-core - ovirt-engine-installer - ovirt-engine-userportal - ovirt-engine-webadmin
Others may follow later.
Talking with Itamar, this mailing list should not accept emails from anyone else and reject them automatically. replies should go to users@ovirt.org for discussion, as dneary suggested.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Hi, On 12/05/2013 08:38 AM, Sandro Bonazzola wrote:
I can't see ovirt-bugs@ovirt.org in http://lists.ovirt.org/mailman/listinfo . The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list?
It's not a mailing list - it's a fictive Bugzilla user that you can follow to get notifications for bugs created by it, I believe. How do other groups handle this? Cheers, Dave. -- 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
Il 05/12/2013 11:42, Dave Neary ha scritto:
Hi,
On 12/05/2013 08:38 AM, Sandro Bonazzola wrote:
I can't see ovirt-bugs@ovirt.org in http://lists.ovirt.org/mailman/listinfo . The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list?
It's not a mailing list - it's a fictive Bugzilla user that you can follow to get notifications for bugs created by it, I believe.
How do other groups handle this?
I don't really know.
Cheers, Dave.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 12/05/2013 12:42 PM, Dave Neary wrote:
Hi,
On 12/05/2013 08:38 AM, Sandro Bonazzola wrote:
I can't see ovirt-bugs@ovirt.org in http://lists.ovirt.org/mailman/listinfo . The user ovirt-bugs@ovirt.org has been created as mailing list user in bugzilla.redhat.com (that user can't login on bugzilla). Can infra team create that list?
It's not a mailing list - it's a fictive Bugzilla user that you can follow to get notifications for bugs created by it, I believe.
I thought it was supposed to be a mailing list which will get all emails and you could register to?
How do other groups handle this?
Cheers, Dave.
participants (4)
-
Dave Neary -
Itamar Heim -
Karsten 'quaid' Wade -
Sandro Bonazzola