New mailing list for the hooks
Hi! We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs. ---- David Caro Red Hat Czech s.r.o. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic RHT Global #: 82-62605
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2NTANTNSMLAEWKFOEDFKX Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 05/27/2013 12:44 PM, David Caro Estevez wrote:
Hi! =20 We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
What name do you need? How do you need it configured? One of these types may work, e.g. a -patch style mailing list? http://www.ovirt.org/Creating_and_configuring_mailing_lists BTW, I think we have a ticket classification in Trac for Mailman work. - Karsten --=20 Karsten 'quaid' Wade http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 ------enig2NTANTNSMLAEWKFOEDFKX 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/ iD8DBQFRpDgO2ZIOBq0ODEERAoa5AKCiz6HhgYuyg3EY0yv4rvi4WShXdwCff27W 2eNKeL8g/AKsmlb8K23yLrg= =Vqp3 -----END PGP SIGNATURE----- ------enig2NTANTNSMLAEWKFOEDFKX--
It should have ovirt and maybe robot or something similar in the name so it's clear that it's not a physical user. robot@ovirt.rg or automation@ovirt.org should be ok. I think that the list should be private in order to avoid someone to change the password of the account in bugzilla and modify bugs. I'll open a track then! David ----- Original Message -----
From: "Karsten 'quaid' Wade" <kwade@redhat.com> To: infra@ovirt.org Sent: Tuesday, May 28, 2013 6:52:30 AM Subject: Re: New mailing list for the hooks
On 05/27/2013 12:44 PM, David Caro Estevez wrote:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
What name do you need?
How do you need it configured? One of these types may work, e.g. a -patch style mailing list?
http://www.ovirt.org/Creating_and_configuring_mailing_lists
BTW, I think we have a ticket classification in Trac for Mailman work.
- Karsten -- Karsten 'quaid' Wade http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 05/28/2013 12:24 PM, David Caro Estevez wrote:
It should have ovirt and maybe robot or something similar in the name so it's clear that it's not a physical user.
robot@ovirt.rg or automation@ovirt.org should be ok.
I think that the list should be private in order to avoid someone to change the password of the account in bugzilla and modify bugs.
I'll open a track then!
this isn't a mailing list that would be open, rather like the gerrit one used for github subscription management for mirroring. the only reason to use it is to approve account registration, etc. hence, private archives, no subscriptions should be approved and the such.
David
----- Original Message -----
From: "Karsten 'quaid' Wade" <kwade@redhat.com> To: infra@ovirt.org Sent: Tuesday, May 28, 2013 6:52:30 AM Subject: Re: New mailing list for the hooks
On 05/27/2013 12:44 PM, David Caro Estevez wrote:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
What name do you need?
How do you need it configured? One of these types may work, e.g. a -patch style mailing list?
http://www.ovirt.org/Creating_and_configuring_mailing_lists
BTW, I think we have a ticket classification in Trac for Mailman work.
- Karsten -- Karsten 'quaid' Wade http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Hi, we said to catch up with this issue on the last meeting, so here it is. I've opened the track too: https://fedorahosted.org/ovirt/ticket/58 ----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "David Caro Estevez" <dcaroest@redhat.com> Cc: "Karsten 'quaid' Wade" <kwade@redhat.com>, infra@ovirt.org Sent: Tuesday, May 28, 2013 3:24:47 PM Subject: Re: New mailing list for the hooks
On 05/28/2013 12:24 PM, David Caro Estevez wrote:
It should have ovirt and maybe robot or something similar in the name so it's clear that it's not a physical user.
robot@ovirt.rg or automation@ovirt.org should be ok.
I think that the list should be private in order to avoid someone to change the password of the account in bugzilla and modify bugs.
I'll open a track then!
this isn't a mailing list that would be open, rather like the gerrit one used for github subscription management for mirroring. the only reason to use it is to approve account registration, etc. hence, private archives, no subscriptions should be approved and the such.
David
----- Original Message -----
From: "Karsten 'quaid' Wade" <kwade@redhat.com> To: infra@ovirt.org Sent: Tuesday, May 28, 2013 6:52:30 AM Subject: Re: New mailing list for the hooks
On 05/27/2013 12:44 PM, David Caro Estevez wrote:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
What name do you need?
How do you need it configured? One of these types may work, e.g. a -patch style mailing list?
http://www.ovirt.org/Creating_and_configuring_mailing_lists
BTW, I think we have a ticket classification in Trac for Mailman work.
- Karsten -- Karsten 'quaid' Wade http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Am Montag, den 27.05.2013, 15:44 -0400 schrieb David Caro Estevez:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
Hey, I joined in late - Is there some documentation on what is planned with the bz hooks? This would also be interesting for oVirt Node. Greetings fabian
On 05/28/2013 02:55 PM, Fabian Deutsch wrote:
Am Montag, den 27.05.2013, 15:44 -0400 schrieb David Caro Estevez:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
Hey,
I joined in late - Is there some documentation on what is planned with the bz hooks? This would also be interesting for oVirt Node.
i think the basics are: if bug-url exists, verify its format and that bug is visible. if bug-url exists, change to post on patch being posted and add a reference to the patch in the bug (external tracker ovirt-gerrit). if bug-url exists, and bug is in product 'ovirt', change bug to modified on patch merge.
Am Dienstag, den 28.05.2013, 16:26 +0300 schrieb Itamar Heim:
On 05/28/2013 02:55 PM, Fabian Deutsch wrote:
Am Montag, den 27.05.2013, 15:44 -0400 schrieb David Caro Estevez:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
Hey,
I joined in late - Is there some documentation on what is planned with the bz hooks? This would also be interesting for oVirt Node.
i think the basics are:
if bug-url exists, verify its format and that bug is visible.
if bug-url exists, change to post on patch being posted and add a reference to the patch in the bug (external tracker ovirt-gerrit).
if bug-url exists, and bug is in product 'ovirt', change bug to modified on patch merge.
Itamar, thanks for the summary, nice work! Mike, +1 from me for also following the Bug-Url-commit-line-convention to also take advantage of this work. Greetings fabian
On 05/28/2013 09:30 AM, Fabian Deutsch wrote:
Am Dienstag, den 28.05.2013, 16:26 +0300 schrieb Itamar Heim:
On 05/28/2013 02:55 PM, Fabian Deutsch wrote:
Am Montag, den 27.05.2013, 15:44 -0400 schrieb David Caro Estevez:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
Hey,
I joined in late - Is there some documentation on what is planned with the bz hooks? This would also be interesting for oVirt Node.
i think the basics are:
if bug-url exists, verify its format and that bug is visible.
if bug-url exists, change to post on patch being posted and add a reference to the patch in the bug (external tracker ovirt-gerrit).
if bug-url exists, and bug is in product 'ovirt', change bug to modified on patch merge.
Itamar, thanks for the summary, nice work!
Mike, +1 from me for also following the Bug-Url-commit-line-convention to also take advantage of this work.
No objection from me.
Greetings fabian
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 05/28/2013 04:35 PM, Mike Burns wrote:
On 05/28/2013 09:30 AM, Fabian Deutsch wrote:
Am Dienstag, den 28.05.2013, 16:26 +0300 schrieb Itamar Heim:
On 05/28/2013 02:55 PM, Fabian Deutsch wrote:
Am Montag, den 27.05.2013, 15:44 -0400 schrieb David Caro Estevez:
Hi!
We also need a new mailing list for the bugzilla hooks account, so we can modify/update the bugs.
Hey,
I joined in late - Is there some documentation on what is planned with the bz hooks? This would also be interesting for oVirt Node.
i think the basics are:
if bug-url exists, verify its format and that bug is visible.
if bug-url exists, change to post on patch being posted and add a reference to the patch in the bug (external tracker ovirt-gerrit).
if bug-url exists, and bug is in product 'ovirt', change bug to modified on patch merge.
Itamar, thanks for the summary, nice work!
david did the work of course.
participants (5)
-
David Caro Estevez -
Fabian Deutsch -
Itamar Heim -
Karsten 'quaid' Wade -
Mike Burns