Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 15 Feb 2015 17:53:24 +0100
From: Luca Barbato <>
Subject: Re: Please consider setting up a bug tracker?

On 15/02/15 17:16, Rich Felker wrote:
> On Sun, Feb 15, 2015 at 05:22:32PM +0200, Jukka Jylänki wrote:
>> Hi,
>> I just recently registered to the musl mailing list to report a bug, since
>> the FAQ here mentioned that there is no
>> separate tracker to report bugs to.
>> Afterwards, I now realize that this was a bad idea, since the sheer amount
>> of uninteresting emails that I began getting make it difficult to filter
>> out the discussion around musl from the potential discussion to the bug I
>> reported, and I find it simplest to unregister from the mailing list after
>> reporting the bug. However, this kind of "fire and forget" bug reporting
>> feels bad, and I lose the way to keep in touch with the communication
>> around the bug.
>> I see that the issue of setting up a bug tracker has already been discussed
>> before here . Has anything
>> changed with this respect?
> No, but I want a bug/patch tracker more than ever right now. There
> have been a lot of patches (and a few bug reports) coming in lately
> and it's hard to keep track of them all manually. So far bugzilla is
> probably the main candidate, but I also looked at a few others. I'd
> welcome input on what works well (both from a user standpoint and from
> an implementation-quality/hosting-considerations standpoint).

I tried to do a run about few months ago and so far bugzilla remains the 
best overall.

If you want to keep the mailinglist workflow you might look at patchwork 
or, once I manage to complete it, plaid.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.