[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Migrating to the gitlab issue tracker

From: Laszlo Ersek
Subject: Re: Migrating to the gitlab issue tracker
Date: Wed, 4 Nov 2020 18:03:26 +0100

On 11/02/20 15:26, 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.

People never subscribed to a particular bug can retroactively learn --
when it turns into an interest for them -- about actions on the bug,
over time. Bug tracker web UIs do not always present such a view. (IOW
it's not interchangeable with retroactively opening the ticket and
reading through it.)

Additionally, mailing list archives can be imported locally, for
indexing / searching, etc. Nothing beats a local search engine that has
access to years of bug traffic. Google may come somewhat close; bug
trackers' own search functionalities are hopeless in comparison (IME).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]