[llvm-dev] RFC: Switching from Bugzilla to Github Issues

[James Henderson via llvm-dev]

+1 to using Anton's list as a starting point. I think the top-level
directories llvm-project + backends are not really fine-grained enough for
some areas. For example, the code related to the various LLVM binary
utilities like llvm-readobj/llvm-objcopy/llvm-symbolizer etc is all
contained within llvm/tools, and wouldn't have their own tag, or even one
closely related ("llvm" would be the tag they'd come under, which is...
less than useful). Separate tags for each tool (possibly with some shared
ones for tools which are broadly aliases like llvm-objcopy/llvm-strip and
llvm-readelf/llvm-readobj etc) would certainly help me. Bugzilla already
has most of these.

On Mon, 28 Oct 2019 at 23:11, Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> > Here are my suggestions for the minimal set of tags:
> >
> > + 1 per LLVM backend
> > + 1 per top-level directory in https://github.com/llvm/llvm-project
> >
> > I think if we start here we can create more specialized tags as
> > GitHub issues gets more traffic and we have more experience using it.
> The google doc I created contains the slightly cleaned list of current
> components. It could be used as a good starting point for defining a
> list of tags.
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191029/f7645913/attachment.html>