This was sent to s...@s.t.o. I've now (tried to) make comm...@s.a.o a subscriber of s...@s.t.o, so that website commits appear on our s.a.o commits list.
cmpil...@tigris.org wrote on Fri, 7 May 2010 at 12:06 -0700: > Author: cmpilato > Date: 2010-05-07 12:06:10-0700 > New Revision: 89 > > Modified: > trunk/www/issue-tracker.html > > Log: > Update issue filing instructions, and fix some formatting. > > Modified: trunk/www/issue-tracker.html > Url: > http://subversion.tigris.org/source/browse/subversion/trunk/www/issue-tracker.html?view=diff&pathrev=89&r1=88&r2=89 > ============================================================================== > --- trunk/www/issue-tracker.html (original) > +++ trunk/www/issue-tracker.html 2010-05-07 12:06:10-0700 > @@ -159,7 +159,7 @@ > >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, > +<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 > @@ -168,10 +168,8 @@ > 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>Severity is represented in the <b>Priority</b> field. Here is how > +priority numbers map to severity:</p> > > <ul> > > @@ -194,14 +192,21 @@ > > </ul> > > -<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 > +<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 (2 / 3)</b>" is not quite the same as > "<b>e2.5 (1 / 4)</b>"!</p> > > </div> > > ------------------------------------------------------ > http://subversion.tigris.org/ds/viewMessage.do?dsForumId=495&dsMessageId=2605179 >
