| <html> |
| <head> |
| <title>Subversion Issue Tracker</title> |
| <link rel="stylesheet" type="text/css" |
| href="http://subversion.tigris.org/branding/css/tigris.css"/> |
| <link rel="stylesheet" type="text/css" |
| href="http://subversion.tigris.org/branding/css/inst.css"/> |
| <link rel="stylesheet" type="text/css" media="print" |
| href="http://subversion.tigris.org/branding/css/print.css"/> |
| <script type="text/javascript" |
| src="http://subversion.tigris.org/branding/scripts/tigris.js"></script> |
| </head> |
| |
| <body> |
| <div class="app"> |
| |
| <h2>Subversion Issue Tracker</h2> |
| |
| <!-- jump to issue form: --> |
| <table border="0" cellspacing="0" cellpadding="3"> |
| <tr> |
| |
| <td id="issueid"> |
| <form method="get" action="http://subversion.tigris.org/issues/show_bug.cgi" tabindex="1"> |
| <input name="id" size="6" tabindex="2" /> |
| <input type="submit" value="Jump to issue" tabindex="3" /> |
| </form> |
| </td> |
| </tr> |
| </table> |
| |
| <h3>Issue Tracker Guidelines</h3> |
| |
| <div class="alert" style="color: black; font-size: 130%; font-weight: bold"> |
| |
| <div style="font-size: 200%; color: red"> |
| <center> |
| <p>Before filing a new issue, please:</p> |
| </center> |
| </div> |
| |
| <ul> |
| |
| <li><p>Re-read the documentation<br> |
| <span style="font-size: 75%; font-weight: normal"> |
| (especially the <a href="/faq.html">FAQ</a> and the |
| online <a href="http://svnbook.red-bean.com/" |
| >Subversion book</a>).</span></p></li> |
| |
| <li><p>Look through <a |
| href="http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED" |
| >existing issues</a><br><span style="font-size: 75%; font-weight: normal"> |
| to see if this bug has already been reported.</span></p></li> |
| |
| <li><p>Report your problem to <a href="mailto:users@subversion.tigris.org" |
| >users@subversion.tigris.org</a>,<br> |
| <span style="font-size: 75%; font-weight: normal"> |
| describing the bug or feature request that you were about to file. |
| People there will ask you questions and help get the bug report |
| into a useful form, after verifying that a new issue is appropriate. |
| <i>(See <a href="http://svn.collab.net/repos/svn/trunk/BUGS" |
| >http://svn.collab.net/repos/svn/trunk/BUGS</a> for how |
| to write a useful bug report.)</i></span></p></li> |
| |
| </ul> |
| |
| <p>We depend on the mailing list as a first level of filtering for our |
| bug tracker. Without it, the tracker would be full of duplicate |
| issues, non-issues, and unreproducible issues. Please help us keep |
| the bug database clean, by always posting to the list first!</p> |
| |
| </div> |
| |
| <p>When mailing the list with a concern, make sure that your e-mail |
| describes your bug or enhancement fully. Provide details about the |
| versions of the relevant software (Subversion, Apache, neon, etc.) |
| that you are using, about your operating system, and about any |
| other thing that might seem pertinent to the issue. If you can |
| provide a script which consistently reproduces a problem, that can |
| be incredibly helpful to those evaluating and/or working on your |
| issue.</p> |
| |
| <p></p> |
| |
| <p>After mailing the list, you should expect your concern to be |
| addressed with relative immediacy. That is, within a few days, you |
| should get feedback on your mail. If indeed you have found a new |
| bug in Subversion, or if your enhancement request is feasible, you |
| will likely be asked to return here and file a new issue in the |
| Issue Tracker.</p> |
| |
| <p>When you file the issue, don't forget to include links to the |
| relevant mailing list threads. Those are important context for |
| anyone reading the issue, and their presence also confirms that the |
| issue <i>has</i> already been discussed on the mailing list. |
| Without them, the issue may get accidentally closed because no one |
| can tell that it is the product of a list discussion. </p> |
| |
| <h3>What the 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><a |
| href="http://subversion.tigris.org/issues/buglist.cgi?target_milestone=1.1" |
| >1.1</a></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 |
| 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 |
| other hand, means that we do not anticipate ever scheduling the issue |
| for a particular release. This also does not mean the issue will |
| never be fixed; it merely means that we don't plan to block any |
| release on it.</p> |
| |
| <p> |
| Severity is represented in the <b>Priority</b> field. Here is how |
| priority numbers map to severity: |
| </p> |
| |
| <p> |
| <ul> |
| |
| <li><b>P1:</b> <i>Prevents work from getting done, causes data |
| loss, or BFI ("Bad First Impression" -- too embarrassing for |
| a 1.0 release).</i> |
| </li> |
| |
| <li><b>P2:</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> |
| |
| <li><b>P4:</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> |
| |
| </ul> |
| </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>"! |
| |
| <h3>Enter the Issue Tracker</h3> |
| |
| <p>And so, with further ado, we give you (drumroll…) the |
| Subversion <a |
| href="http://subversion.tigris.org/servlets/ProjectIssues">Issue |
| Tracker</a>.</p> |
| |
| </div> |
| </body> |
| </html> |
