On 02/26/2018 04:17 PM, Christopher Li wrote: > On Mon, Feb 26, 2018 at 3:47 PM, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: >> >> Hi, >> >> Is there any concensus on this? I'll be happy to request it or I'll leave that >> up to Chris, either way, but I haven't done it yet and won't until it's clear >> (at least to me) that it is wanted. > > The consensus is we should have one. Nobody has express strong preference > of what bug tracking system to use. In that case we can go with the > korg bugzilla > because sparse repository, release binary and wiki are already hosted on korg. > Bugzilla can also cross reference the related kernel bug number if there is one. > > Randy, how about you take the lead on sending email to ftpadmin? If we want > to use kernel bugzilla for tracking sparse issue, what is the process and best > practices etc. OK, I made the request. We'll see how it goes. Like Dibyendu has already done, to use it (other than just to view/read it), you (every user) will need to register, then you can just enter or update bug entries. We might need to be able to assign bug owner(s) and possibly even define Component IDs (if Sparse is listed as a Product Category, which is what I requested). Sadly I don't know much about best practices. Some portions of the Linux kernel community use bugzilla.kernel.org (e.g., ACPI) and other just say something like, "Please stick to the [project] mailing list." And some projects have an automated gateway for bugzilla<->email reply/update, which I also asked about. If anyone has specific questions, comments, or suggestions, please email them. thanks, -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
