On 11/2/20 8:26 AM, Daniel P. Berrangé wrote: > On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: >> On 10/30/20 10:16, Stefan Hajnoczi wrote: >>> On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: >>>> In experimenting with my mirror on gitlab though, I was unable to find a >>>> way >>>> to configure it to send issue tracker notifications to the email list. A >>>> move to gitlab would likely mean, then: >>>> >>>> 1. The cessation of (automatic) issue tracker mails to the list >>> >>> A bot could do this. >> >> I think a "bug traffic" mailing list (possibly but not necessarily >> separate from the main qemu development list) is important. > > What benefit is there to a bug traffic mailing list, as opposed to people > subscribing to direct bug notifications ? In both case people who are > interested in watching bugs can get the same content in their inboxes.
A mailing list would have archives (which can be helpful for archaeology of past bug traffic even when you were not a gitlab subscriber), and (depending on subscription settings) could permit additional conversation in response to traffic by non-gitlab contributors. But you are right that a mailing list configured as read-only bug traffic (where replies are not permitted) has no benefit over developers directly subscribing to bug activity. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
