Better distinguish links to issue tracking vs tracker
Our documentation page about how we track issues (issue tracking) was
often referred to as the issue tracker and in several places used an
external link style. That made it hard to know if the link would go to
the actual issue tracker or to the site page that describes our issue
tracking process.
Fix the links to have consistent format and naming and add links to the
actual issue tracker or site page as appropriate. Also add a link to the
contributing page from the bug-fixing page since those are closely
related.
Change-Id: I16e7df3f5e4403706732a7ccab11009fcab75ab7
diff --git a/pages/site/community/bug-fixing.md b/pages/site/community/bug-fixing.md
index 726077c..8c9adf5 100644
--- a/pages/site/community/bug-fixing.md
+++ b/pages/site/community/bug-fixing.md
@@ -9,8 +9,11 @@
## Who is allowed to fix bugs?
Anyone who has accepted [the CLA for the Gerrit Code Review project](https://gerrit-review.googlesource.com/Documentation/dev-cla.html)!
-If you feel like contributing and need a place to start you will always find bugs that need
-fixing, big and small, on the [issue-tracker](https://www.gerritcodereview.com/issues.html).
+If you feel like [contributing](/contributing.html) and need a place to start
+you will always find bugs that need fixing, big and small, on the
+[issue tracker](https://issues.gerritcodereview.com/). For more information on
+how the project uses the tracker, see the [Issue Tracking][issue-tracking]
+documentation.
_Consider bugs in "accepted" state first since these have already been through triage._
@@ -26,8 +29,8 @@
This will announce to everyone else that you are working on the bug, which most likely will
make other affected users very happy which is always positive.
-If there is no issue for the bug you want to fix you'll need to create one first in the
-[issue-tracker](https://www.gerritcodereview.com/issues.html).
+If there is no issue for the bug you want to fix you'll need to create one first.
+See the [Issue Tracking][issue-tracking] documentation for more information.
### 2. Find the earliest supported branch that has the bug
@@ -92,3 +95,5 @@
Severe bugs and [security issues](https://gerrit-review.googlesource.com/Documentation/dev-processes.html#security-issues)
are on occasion fixed in branches that are EOL since we try to offer some support to instances that
haven't been able to migrate to a supported version yet.
+
+[issue-tracking]: /issues.html
diff --git a/pages/site/issues.md b/pages/site/issues.md
index af4f490..eec3b97 100644
--- a/pages/site/issues.md
+++ b/pages/site/issues.md
@@ -6,10 +6,10 @@
toc: false
---
-[Issues][list] are tracked in the Gerrit Code Review Tracker at
-https://issues.gerritcodereview.com/.
+[Issues][list] are tracked in the [Gerrit Code Review Issue Tracker][tracker].
[list]: https://issues.gerritcodereview.com/issues?q=status:open
+[tracker]: https://issues.gerritcodereview.com/
## Status
diff --git a/pages/site/support.md b/pages/site/support.md
index 8c7b77a..60c4864 100644
--- a/pages/site/support.md
+++ b/pages/site/support.md
@@ -9,7 +9,7 @@
## Quick Links
* [Mailing list][repo-discuss]
-* [Issue tracker][issue-tracking]
+* [Issue Tracking][issue-tracking]
## Supported Versions
@@ -86,10 +86,10 @@
If the issue/question you posted on Repo Discuss is considered a bug
the community will ask you to create an issue for tracking it.
-Bugs are reported to the [issue tracker][issue-tracking].
-The issue tracker is not always the best place to initially request
-new features, as the main focus for those consuming it is fixing
-bugs.
+Bugs are reported to the [issue tracker][issue-tracker]. The issue tracker is
+not always the best place to initially request new features, as the main focus
+for those consuming it is fixing bugs. See the [issue tracking][issue-tracking]
+documentation for more information.
## New Features
@@ -226,7 +226,7 @@
GerritForge provides free Community Support (CS) for the Gerrit community using
two channels:
1. [Repo-discuss mailing list](https://groups.google.com/g/repo-discuss)
-2. [Gerrit issue-tracker](https://bugs.chromium.org/p/gerrit)
+2. [Gerrit issue-tracker][issue-tracker]
GerritForge monitors the channels *on UK and EU working days, 8:00-23:00 GMT*,
and occasionally over week-ends and bank holidays.
@@ -273,6 +273,7 @@
[feature-request]: https://gerrit-review.googlesource.com/Documentation/dev-design-docs.html#propose
[issue-tracking]: /issues.html
+[issue-tracker]: https://issues.gerritcodereview.com/
[repo-discuss]: https://groups.google.com/forum/#!forum/repo-discuss
[discord-server]: https://discord.gg/HkGbBJHYbY
[stack-overflow]: https://stackoverflow.com/questions/tagged/gerrit
