On 02/10/2015 01:49, Stefan wrote:
Hi,
the attached patch updates the issues.html page to reflect the
migration to JIRA by:
- updating the issue tracker states
- updating the link to get the currently open issues
- replace names of issue tracker fields which differ from the bugzilla
ones
in addition the patch also updates the milestones/versions so they
look a bit more up-to-date (1.9.x-example -> 1.10.x).
Regards,
Stefan
Updated based on danielsh's feedback:
- no rewrapping of lines
- dropped the 1.9.x -> 1.10.x change
Regards,
Stefan
Index: issues.part.html
===================================================================
--- issues.part.html (revision 1706325)
+++ issues.part.html (working copy)
@@ -228,8 +228,8 @@
title="Link to this section">¶</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,13 +343,13 @@
<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="http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&order=issues.target_milestone%2C%20issues.priority%2C%20issues.issue_type";
+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
been resolved already, etc. For each issue that will remain open, it
also means making sure that the various fields are set appropriately:
-type, subcomponent, platform, OS, version, keywords (if any), and so
+type, component, environment, version, labels (if any), and so
on.</p>
<p>Here's an overview of the process (in this example, 1.5 is the next
@@ -376,7 +376,7 @@
# 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.
