subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julianf...@apache.org
Subject svn commit: r1706908 - in /subversion/site/publish: docs/community-guide/issues.part.html reporting-issues.html
Date Mon, 05 Oct 2015 19:46:49 GMT
Author: julianfoad
Date: Mon Oct  5 19:46:49 2015
New Revision: 1706908

URL: http://svn.apache.org/viewvc?rev=1706908&view=rev
Log:
Update references to the issue tracker on our web site to point to JIRA on
ASF, following the recent migration from Issuezilla on Tigris.

Some of these changes were
Suggested by: luke1410

* publish/docs/community-guide/issues.part.html
  (reporting-bugs): Update links to the old Tigris web page to point to
    'reporting-issues.html' instead.
  (milestones-open,
   issue-triage): Use the new names for issue statuses. Change a query link
    to use 'resolution=Unresolved' instead of 'status in ...'.

* publish/reporting-issues.html
  (queries): Change query links to use 'resolution=Unresolved' instead of
    'status in ...' and to sort by priority.

Modified:
    subversion/site/publish/docs/community-guide/issues.part.html
    subversion/site/publish/reporting-issues.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=1706908&r1=1706907&r2=1706908&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Mon Oct  5 19:46:49 2015
@@ -83,7 +83,7 @@ mailing list first, <a href="mailto:user
 href="irc://irc.freenode.net/#svn">irc.freenode.net, channel #svn</a>.</p>
 
 <p>You should
-also <a href="http://subversion.tigris.org/issue-tracker.html#find"
+also <a href="http://subversion.apache.org/reporting-issues.html#queries"
 >search in the bug tracker</a> to see if anyone has already reported
 this bug.</p>
 
@@ -141,7 +141,7 @@ href="<!--#echo var="GUIDE_GENERAL_PAGE"
 href="mailto:dev@subversion.apache.org"
 >dev@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
+href="http://subversion.apache.org/reporting-issues.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
@@ -163,7 +163,7 @@ make the bug much more likely to get fix
     <a href="mailto:users@subversion.apache.org"
                    >users@subversion.apache.org</a>.
     Once it's confirmed as a bug, someone, possibly you, can enter it
-    into the <a href="http://subversion.tigris.org/issue-tracker.html"
+    into the <a href="http://subversion.apache.org/reporting-issues.html"
     >issue tracker</a>.  (Or if you're pretty sure about the bug, go
     ahead and post directly to our development
     list, <a href="mailto:dev@subversion.apache.org"
@@ -228,8 +228,8 @@ understand those distinctions.</p>
     title="Link to this section">&para;</a>
 </h3>
 
-<p>For open issues (those whose status is <tt>UNCONFIRMED</tt>,
-<tt>NEW</tt>, <tt>STARTED</tt> or <tt>REOPENED</tt>),
the milestone
+<p>For open issues (those whose status is <tt>OPEN</tt>,
+<tt>IN PROGRESS</tt>, or <tt>REOPENED</tt>), the milestone
 indicates the Subversion release for which the developers are
 targeting the resolution of that issue.  In the general case, we use
 milestones of the form <tt><em>MINORVERSION</em>-consider</tt> to
@@ -343,7 +343,7 @@ do.</p>
 <p>The unmilestoned issues are listed first when you sort by
 milestone, and <em>issue triage</em> is the process of trawling
 through all the <a
-href="https://issues.apache.org/jira/issues?jql=project%20%3D%20SVN%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)"
+href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC"
 >open issues</a> (starting with the unmilestoned ones), determining
 which are important enough to be fixed now, which can wait until
 another release, which are duplicates of existing issues, which have
@@ -361,7 +361,7 @@ release, so urgent issues would go there
         close_as_dup(i)
       elif issue_is_invalid(i):
         # A frequent reason for invalidity is that the reporter
-        # did not follow the <a href="http://subversion.tigris.org/issue-tracker.html#buddy-system">"buddy
system"</a> for filing.
+        # did not follow the <a href="http://subversion.apache.org/reporting-issues.html">"buddy
system"</a> for filing.
         close_as_invalid(i)
       elif issue_already_fixed(i):
         version = fixed_in_release(i)
@@ -376,7 +376,7 @@ release, so urgent issues would go there
 
       # Else issue should remain open, so DTRT with it...
 
-      # Set priority, platform, subcomponent, etc, as needed.
+      # Set priority, environment, component, etc, as needed.
       adjust_all_fields_that_need_adjustment(i)
 
       # Figure out where to put it.

Modified: subversion/site/publish/reporting-issues.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/reporting-issues.html?rev=1706908&r1=1706907&r2=1706908&view=diff
==============================================================================
--- subversion/site/publish/reporting-issues.html (original)
+++ subversion/site/publish/reporting-issues.html Mon Oct  5 19:46:49 2015
@@ -83,11 +83,12 @@
 
 <ul>
 <li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN">All
issues</a></li>
-<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29">Open
issues</a></li>
-<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29%20AND%20fixVersion%20%3D%20---">Issues
in need of triaging</a></li>
-<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29%20AND%20labels%20%3D%20bite-sized">Issues
that might be relatively easy to fix</a></li>
-<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29%20AND%20labels%20%3D%20patch">Issues
that have associated patches</a></li>
-<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Resolved%2C%20Closed%29">Closed
issues</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC"
+>Open issues</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20---%20ORDER%20BY%20priority%20DESC">Issues
in need of triaging</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20bite-sized%20ORDER%20BY%20priority%20DESC">Issues
that might be relatively easy to fix</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20patch%20ORDER%20BY%20priority%20DESC">Issues
that have associated patches</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20ORDER%20BY%20priority%20DESC">Closed
issues</a></li>
 </ul>
 
 



Mime
View raw message