[Lldb-commits] [PATCH] D116351: Update Bug report URL to Github Issues

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

Quuxplusone accepted this revision.
Quuxplusone added a comment.

Tweaked English wording throughout. LGTM with all these modifications made.

Orthogonally, it does occur to me that one might save a //lot// of this churn (and also the next time the bug tracker moves, e.g. if we go from GitHub to something else) by simply HTTP-redirecting the front page of https://bugs.llvm.org/ to https://github.com/llvm/llvm-project/issues/ . Then we'd have a stable URL https://bugs.llvm.org/ for "reporting LLVM bugs, forever," and we could just use that stable URL everywhere. But OTOH, that's a devops task, whereas updating a bunch of documentation in the repo is easy. :)



================
Comment at: clang-tools-extra/docs/clang-doc.rst:15
 crashes. Submitting reports with information about how to reproduce the issue
-to `the LLVM bugtracker <https://bugs.llvm.org/>`_ will definitely help the
+to `the LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_ will definitely help the
 project. If you have any ideas or suggestions, please to put a feature request
----------------
Please leave the English wording as "the LLVM bugtracker" (or "the LLVM bug tracker" — really it should be two words). There is no such noun in English as "an Issues," which means that the reader won't have any idea what you're talking about here unless they click on the link to see where it goes.


================
Comment at: clang/www/c_status.html:75-76
 
-<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> contains a
-Clang C component that tracks known bugs with Clang's language
+<p>The <a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contains
+issuses labeled with c/c11/c18/c2x that tracks known bugs with Clang's language
 conformance.</p>
----------------



================
Comment at: clang/www/cxx_status.html:79-81
+<p>The <a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contains
+issues labelled with c++/c++11/c++14/c++17/c++20 that track known bugs with Clang's
+language conformance labelled in each language mode.</p>
----------------
(I think `, "C++17", "C++20", "C++23"` would just be redundant/noise here, and would imply a thankless task for someone to go update this list every 3 years. Better to just cap it at one or two labels. The reader can be trusted to figure out that C++20 issues should be labeled with `C++20`.)


================
Comment at: clang/www/get_involved.html:68
 href="OpenProjects.html">Open Projects</a> page or look through the <a
-href="https://bugs.llvm.org/">Bugzilla bug database</a>.</p>
+href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a>.</p>
 
----------------



================
Comment at: clang/www/get_started.html:22
 involved</a> with the Clang community.  If you run into problems, please file
-bugs in <a href="https://bugs.llvm.org/">LLVM Bugzilla</a>.</p>
+bugs in <a href="https://github.com/llvm/llvm-project/issues">LLVM Issues</a>.</p>
 
----------------



================
Comment at: libcxx/docs/index.rst:220
 * `libc++abi Homepage <http://libcxxabi.llvm.org/>`_
-* `LLVM Bugzilla <https://bugs.llvm.org/>`_
+* `LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_
 * `libcxx-commits Mailing List`_
----------------



================
Comment at: libunwind/docs/index.rst:101
 * `LLVM Homepage <https://llvm.org/>`_
-* `LLVM Bugzilla <https://bugs.llvm.org/>`_
+* `LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_
 * `cfe-commits Mailing List`_
----------------



================
Comment at: lld/docs/_templates/indexsidebar.html:3-4
 
 <p>lld bugs should be reported at the
-  LLVM <a href="https://bugs.llvm.org/">Bugzilla</a>.</p>
+  LLVM <a href="https://github.com/llvm/llvm-project/issues/">Issues</a>.</p>
----------------



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

https://reviews.llvm.org/D116351