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

Paul Robinson via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Jan 20 17:46:43 PST 2022


probinson added inline comments.


================
Comment at: llvm/docs/BugLifeCycle.rst:80
 
-* CC others not already cc’ed that you happen to know would be good to pull in.
-* Add the "beginner" keyword if you think this would be a good bug to be fixed
+* Add the ``beginner`` label if you think this would be a good bug to be fixed
   by someone new to LLVM.
----------------
Quuxplusone wrote:
> As Tom says, please use [good first issue] here instead. It is meaningful to GitHub: it populates https://github.com/llvm/llvm-project/contribute and several third-party websites aimed at new FOSS contributors.
> 
> [beginner], by contrast, came from a Bugzilla keyword during the migration. I don't know for sure what its original intent was, but I agree it seems like a synonym for [good first issue]. (And therefore I suggest we retag all 89 open [beginner] issues as [good first issue] and then burninate the [beginner] tag. But I won't do that unless someone tells me to. ;))
There's a similar debate on Discourse, https://llvm.discourse.group/t/good-first-issue-vs-beginner/5850

But I'd say: Do it. :)


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D117832



More information about the llvm-commits mailing list