[PATCH] D117832: Update the Bug Life Cycle docs for the switch to GitHub issues

Thu Jan 20 14:25:15 PST 2022

Quuxplusone added inline comments.

================
Comment at: llvm/docs/BugLifeCycle.rst:44

-Make sure that you have one or more people on cc on the bug report that you
-think will react to it. We aim to automatically add specific people on cc for
-most products/components, but may not always succeed in doing so.
-
-If you know the area of LLVM code the root cause of the bug is in, good
-candidates to add as cc may be the same people you'd ask for a code review in
-that area. See :ref:`finding-potential-reviewers` for more details.
-
+You can apply labels to the bug to provide extra information to make the bug
+easier to discover, such as a label for the part of the project the bug
----------------
Argh, sorry for the multi-posting as I keep thinking of things to say here!

Let's make "labels" a hyperlink to https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels
which incidentally describes the meanings of GitHub's default labels.

The only one of them where it appears we're not using it as its "originalist" meaning is [question], which apparently "originally" meant something like "The maintainer has a question for the submitter" but in our case we're clearly using it to tag, duh, questions. https://github.com/llvm/llvm-project/labels/question  I would be very cool with burninating [question] and merging it into [invalid]; is that too harsh? :)

I'm relatively cool with the idea of tagging everything as either [bug] or [enhancement], but it's going to make for a lot of tough calls in practice. Right now we also have [new-feature] and [missing-feature], which I think are arguably the same as [enhancement]?
How would you categorize "Your `-std=c++20` mode doesn't support half of C++20" — //bug//, or request for someone to implement the missing //features//? Further, consider "This existing feature is good but it could be better," versus "This feature doesn't exist today but I would like it to exist." Are those both "enhancements" or is there a category difference worth reflecting in the labels?  Basically all [clang:diagnostics] issues are both-bug-and-feature-request in this way.

Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D117832/new/

https://reviews.llvm.org/D117832