[clangd-dev] Bug tracking: bugzilla, github, ???

Kirill Bobyrev via clangd-dev clangd-dev at lists.llvm.org
Fri Oct 12 06:20:04 PDT 2018

Hi Sam,

I also think that bug tracking for Clangd is not in the best shape and it
would certainly be great to improve the process. However, I think that this
is true for most (if not all) LLVM & Clang components, so there's a room
for improvement. You might be interested in a relevant discussion
<https://lists.llvm.org/pipermail/llvm-dev/2018-October/126732.html> on
LLVM bug lifecycle via llvm-dev.

I agree that creating a GitHub page for Issues would improve the process,
but I am not sure whether the improvement will be significant. This would
also make the whole process less obvious for developers and bug reporters
since the process would be different from the "traditional" LLVM/Clang
experience while Clangd is not clearly different from the rest of the
tooling (e.g. it lives in the same clang-tools-extra repo).

I can't think of anything better at this point and I would certainly be
interested to learn what others think about it.


On Fri, Oct 12, 2018 at 11:18 AM Sam McCall via clangd-dev <
clangd-dev at lists.llvm.org> wrote:

> Currently I don't think we do much bug tracking at all - there are a few
> old issues in bugzilla.
> If we announce clangd as suitable for general consumption, start shipping
> with YCM etc for LLVM 8, we should have a reasonable channel to collect
> feedback and bugs.
> I'm not sure bugs.llvm.org is the right thing for an end-user tool:
>    - bugzilla is an unfamiliar tool that's not part of developers'
>    workflow
>    - there's no way to post a bug as a new user without emailing a human
>    to set up an account
>    - you have to be familiar with llvm's project structure to file a bug
> The most obvious alternative is github issues, as ~everyone has an account
> and has used the bug tracker, and it's friendly to casual new users.
> I *think* the easiest setup would be a separate "clangd" repo just for
> issue tracking and maybe docs, rather than having to fish issues out of a
> big llvm monorepo.
> Anyone have thoughts here? Particularly: anyone want to argue that
> bug/feature tracking is unimportant, or that the status quo is viable?
> Cheers, Sam
> _______________________________________________
> clangd-dev mailing list
> clangd-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/clangd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20181012/adfe75f3/attachment.html>

More information about the clangd-dev mailing list