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

[Arthur O'Dwyer via Phabricator via llvm-commits]

Quuxplusone added inline comments.


================
Comment at: llvm/docs/BugLifeCycle.rst:122-125
+Please add the ``infrastructure`` label to request any changes to be made to
+the labels used by the issue tracker instead of creating your own label. This
+increases consistency when triaging and helps reduce the proliferation of
+labels.
----------------
Quuxplusone wrote:
> I think this is saying: Any project member can create new labels, but we discourage it, because we don't want a proliferation of similar or single-use labels. If you are not a project member — or even if you are! — then when you want a new label created, please open a GitHub issue with the subject line "Create issue label [foo]", add the [infrastructure] label to that issue itself, and wait. (For what, exactly?)
> 
> My impression is that a better/faster alternative is to speak up in the #infrastructure channel on the Discord.
Oh, and every new label request should include a description of //what the label is for//, which will be used as its description on https://github.com/llvm/llvm-project/labels . If you're ever unsure of the meaning of a label, visit https://github.com/llvm/llvm-project/labels for more information.

(And post-migration corollary: if you //know// the intent of label [foo] but it's not actually documented on https://github.com/llvm/llvm-project/labels , then please edit its documentation there so that future readers //will// be able to find it!)


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D117832