> I (Julian Foad) wrote: >> I've updated the ASF web site: http://svn.apache.org/r1706376
The attached patch updates the 'issue-tracker.html' page on Tigris. However, my commit attempt fails although I have a login and password, presumably because the project is locked. Mark, can we temporarily unlock it and (you or I) commit this? Patch log message: [[[ Update references to the issue tracker on our web site to point to JIRA on ASF, following the recent migration from Issuezilla on Tigris. * www/issue-tracker.html Update to point to the new JIRA issue tracker. Add the new priority keywords against the old priority numbers. Remove obsolete information about requesting 'Observer' role, filing 'Patch' issues, and putting Effort estimates in the Status Whiteboard. ]]] Ivan Zhakov wrote: > I think it would be nice to merge updated content on > http://subversion.tigris.org/issue-tracker.html to > reportoing-issues.html page. Yes, that would be nice, if anybody wants to do it. >> I already noticed my HTML foo is weak: when submitting a query with >> the second "submit" button on >> subversion.apache.org/reporting-issues.html, as well as correctly >> opening the query result page (ino a new window/tab), the query string >> gets put as a query argument on the *current* page's URL. >> >> Anyone want to help fix up that HTML? > > Do we really need this forms on reporting-issues.html page? We don't really need these forms, but presumably somebody once thought it was useful to add them. I don't mind if somebody removes them. - Julian
Update references to the issue tracker on our web site to point to JIRA on ASF, following the recent migration from Issuezilla on Tigris. * www/issue-tracker.html Update to point to the new JIRA issue tracker. Add the new priority keywords against the old priority numbers. Remove obsolete information about requesting 'Observer' role, filing 'Patch' issues, and putting Effort estimates in the Status Whiteboard. --This line, and those below, will be ignored-- Index: www/issue-tracker.html =================================================================== --- www/issue-tracker.html (revision 132) +++ www/issue-tracker.html (working copy) @@ -10,13 +10,13 @@ <div class="h2"> <h2>Subversion Issue Tracker</h2> <!-- jump to issue form: --> <form method="get" style="display: inline;" - action="http://subversion.tigris.org/issues/show_bug.cgi"; > + onsubmit="this.action='https://issues.apache.org/jira/browse/SVN-'+this.id.value;" > <div style="display: inline;"> <input name="id" size="6" /> <input type="submit" value="Jump to issue" /> </div> </form> @@ -50,27 +50,21 @@ Before filing a new issue, please: <li> <div id="find" title="find"> <p><strong>Search the issue tracker:</strong></p> <ul> <li><p><a - href="http://subversion.tigris.org/issues/buglist.cgi?resort=1&component=subversion;issue_status=UNCONFIRMED;issue_status=NEW;issue_status=STARTED;issue_status=REOPENED;issue_status=RESOLVED;issue_status=VERIFIED;issue_status=CLOSED;email1=;emailtype1=substring;emailassigned_to1=1;email2=;emailtype2=substring;emailreporter2=1;issueidtype=include;issue_id=;changedin=;votes=;chfieldfrom=;chfieldto=Now;chfieldvalue=;short_desc=;short_desc_type=substring;long_desc=;long_desc_type=substring;issue_file_loc=;issue_file_loc_type=substring;status_whiteboard=;status_whiteboard_type=substring;keywords=;keywords_type=anytokens;field0-0-0=noop;type0-0-0=noop;value0-0-0=;newqueryname=;Submit%20query=Submit%20query&order=issues.issue_status%2C%20issues.issue_id"; - >List all existing issues</a></p></li> - <li><form method="get" - action="http://subversion.tigris.org/issues/buglist.cgi";> + href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN"; + >Browse or query the existing issues</a></p></li> + <li><form onsubmit="window.open('https://issues.apache.org/jira/issues/?jql=project = SVN AND text ~ '+this.searchText.value);"> <div> <p> <input type="submit" value="Search issue summaries:" /> - <input type="hidden" name="component" value="subversion" /> - <input type="hidden" name="short_desc_type" value="substring" /> - <input type="hidden" name="cmdtype" value="doit" /> - <input name="short_desc" /> + <input name="searchText" /> </p> </div></form></li> - <li><p><a href="http://subversion.tigris.org/issues/query.cgi"; - >Structured query of issues database</a></p></li> </ul> </div> <!-- find --> </li> <li><p><strong>Find someone else who agrees this is a bug.</strong> Post to the <a href="mailto:[email protected]" @@ -122,48 +116,28 @@ helpful to those evaluating and/or worki </div> <div class="h3" id="write-access" title="write-access"> <h3>Filing New Issues, Modifying Existing Issues</h3> -<p>You must be <a href="http://subversion.tigris.org/servlets/Login"; ->logged in to the web site</a> to add a new issue, or to comment on -existing issues. To modify existing issues beyond simply leaving a -comment — e.g., to change fields or -status — you must be both logged in and have the -<em>Observer</em> role in the Subversion project; this is true even -for issues that you created yourself.</p> - -<p>Here's how to acquire the <em>Observer</em> role:</p> - -<ol> - <li><a href="http://subversion.tigris.org/servlets/Login"; - >Log in</a> on the tigris.org site</li> - <li>Go to the Subversion project front page</li> - <li>Click on the <em>Request project role</em> link directly below the - "Project Home" line</li> - <li>Request the <em>Observer</em> role</li> - <li>Wait for the confirmation e-mail (almost always will be - completed within 24 hours)</li> -</ol> +<p>You must be <a href="https://issues.apache.org/jira/login.jsp"; +>logged in to the issue tracker</a> to add a new issue, or to comment on +existing issues. </div> <div class="h3" id="fields" title="fields"> <h3>What the Issue Fields Mean</h3> <p>When an issue is first filed, it automatically goes in the <b>"---"</b> target milestone, which indicates that the issue has not yet been processed. A developer will examine it and maybe talk to other developers, then estimate the bug's severity, the effort required to fix it, and schedule it in a numbered milestone, for -example <b>1.1</b>. (Or they may put it the <b><a -href="http://subversion.tigris.org/issues/buglist.cgi?target_milestone=unscheduled"; ->unscheduled</a></b> or <b><a -href="http://subversion.tigris.org/issues/buglist.cgi?target_milestone=nonblocking"; ->nonblocking</a></b> milestone, if they consider it tolerable for all +example <b>1.1</b>. (Or they may put it the <b>unscheduled</b> or +<b>nonblocking</b> milestone, if they consider it tolerable for all currently planned releases.) </p> <p>An issue filed in <b>unscheduled</b> might still get fixed soon, if some committer decides they want it done. Putting it in <b>unscheduled</b> merely means it hasn't been scheduled for any particular release yet. The <b>nonblocking</b> milestone, on the @@ -174,62 +148,45 @@ release on it.</p> <p>Severity is represented in the <b>Priority</b> field. Here is how priority numbers map to severity:</p> <ul> - <li><b>P1:</b> <i>Prevents work from getting done, causes data + <li><b>P1 Blocker:</b> <i>Prevents work from getting done, causes data loss, or BFI ("Bad First Impression").</i> </li> - <li><b>P2:</b> <i>Workaround required to get stuff done.</i> + <li><b>P2 Critical:</b> <i>Workaround required to get stuff done.</i> </li> - <li><b>P3:</b> <i>Like P2, but rarely encountered in normal usage.</i> + <li><b>P3 Major:</b> <i>Like P2, but rarely encountered in normal usage.</i> </li> - <li><b>P4:</b> <i>Developer concern only, API stability or + <li><b>P4 Minor:</b> <i>Developer concern only, API stability or cleanliness issue.</i> </li> - <li><b>P5:</b> <i>Nice to fix, but in a pinch we could live with it.</i> + <li><b>P5 Trivial:</b> <i>Nice to fix, but in a pinch we could live with it.</i> </li> </ul> -<p>Note that we <strong>do not use the PATCH issue type</strong>. -Please select one of the other relevant issue types (DEFECT, -ENHANCEMENT, or FEATURE). If you happen to have a patch to attach to -an issue, or wish to point folks to a patch for the issue that's been -submitted to the mailing list, then add the "patch" keyword to the -issue. Then, attach the patch or reference the mailing list archive -URL of the patch-bearing message as needed.</p> - -<p>Effort Required is represented in the <b>Status Whiteboard</b> with -an "<b>e number</b>", which is the average of the most optimistic and -most pessimistic projections for number of engineer/days needed to fix -the bug. The e number always comes first, so we can sort on the -field, but we include the actual spread after it, so we know when -we're dealing with a wide range. For example -"<b>e2.5 (2 / 3)</b>" is not quite the same as -"<b>e2.5 (1 / 4)</b>"!</p> - </div> </div> <div class="h2" id="enter" title="enter"> <h2>Enter the Issue Tracker</h2> <p>And so, with further ado, we give you (drumroll…) the Subversion <a - href="http://subversion.tigris.org/servlets/ProjectIssues";>Issue + href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN";>Issue Tracker</a>.</p> <p><i>Again, remember that to add or modify issues, you must be <a -href="#write-access">logged into the website</a>.</i></p> +href="#write-access">logged into the issue tracker</a>.</i></p> </div> </div> </body> </html>
