Author: luke1410
Date: Fri Oct 2 00:25:39 2015
New Revision: 1706337
URL: http://svn.apache.org/viewvc?rev=1706337&view=rev
Log:
Several small corrections/updates to the Bugs/Issues page.
* docs/community-guide/issues.part.html
(How to report a bug): use lower case for "issue tracker"
(Where to report a bug): make HTTPD-statement apply to any 2.x version
(Milestone management): added missing "to" in "to point *to* that previous"
(Issue triage): removed "as" in "close_as_it_for_that_reason"
Approved by: danielsh
Modified:
subversion/site/publish/docs/community-guide/issues.part.html
Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=1706337&r1=1706336&r2=1706337&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Fri Oct 2
00:25:39 2015
@@ -141,8 +141,8 @@ href="<!--#echo var="GUIDE_GENERAL_PAGE"
href="mailto:d...@subversion.apache.org";
>d...@subversion.apache.org</a>, or if you have already been there and
been asked to file an issue, then go to the <a
-href="http://subversion.tigris.org/issue-tracker.html";>Issue
-Tracker</a> and follow the instructions there.</p>
+href="http://subversion.tigris.org/issue-tracker.html";>issue
+tracker</a> and follow the instructions there.</p>
<p>Thanks. We know it's a lot of work to file an effective bug
report, but a good report can save hours of a developer's time, and
@@ -188,7 +188,7 @@ make the bug much more likely to get fix
<a href="mailto:d...@subversion.apache.org";
>d...@subversion.apache.org</a>.</p></li>
-<li><p>If the bug is in Apache HTTPD 2.0, please report it to both of
+<li><p>If the bug is in Apache HTTPD 2.x, please report it to both of
these mailing lists: <a href="mailto:d...@httpd.apache.org";
>d...@httpd.apache.org</a>,
<a href="mailto:d...@subversion.apache.org";
@@ -316,7 +316,7 @@ states. An open issue that's been resol
milestone adjusted to reflect the Subversion release which will first
reflect that change. A resolved issue that gets backported to a
previous release stream needs to have its milestone adjusted to point
-that previous release's version number. Finally, a resolved issue
+to that previous release's version number. Finally, a resolved issue
that gets <tt>REOPENED</tt> needs to have its milestone reevaluated in
terms of whether the issue is a release blocker
(<tt><em>MINORVERSION</em>.0</tt>) or not
@@ -372,7 +372,7 @@ release, so urgent issues would go there
elif issue_is_real_but_we_won't_fix_it(i):
close_as_wontfix(i)
elif issue_is_closeable_for_some_other_reason(i):
- close_as_it_for_that_reason(i)
+ close_it_for_that_reason(i)
# Else issue should remain open, so DTRT with it...
