Changes between Version 6 and Version 7 of WorkingConventions/BugTracker


Ignore:
Timestamp:
Aug 19, 2013 7:53:33 AM (2 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/BugTracker

    v6 v7  
    4141
    4242 * '''Test Case''': fill in this field with the name of the test in the test suite.  Typically every bug
    43    closed should have an appropriate test case added to the test suite.
    44 
    45  Typically we name the regression the same as the ticket (eg "T7901" for #7901), but the test case field
    46    * is a quick check that there IS a regression test
    47    * works even if the test is named differently (in the case of #7901 `ParserNoForallUnicode`)
    48    * works if there are multiple tests
    49    * tells which directory to look in (in the case of #7901 parser/should_fail)
     43   closed should have an appropriate test case added to the test suite.[[BR]][[BR]]
     44 Typically we name the regression the same as the ticket (eg "T7901" for #7901), but the test case field:
     45    * is a quick check that there IS a regression test
     46    * works even if the test is named differently (eg `ParserNoForallUnicode` in the case of #7901)
     47    * works if there are multiple tests
     48    * tells which directory to look in (eg `parser/should_fail` in the case of #7901)
    5049
    5150 * '''cc''': we pay more attention to tickets with a long cc list, so add yourself to the cc list if you care about the ticket.  It is ''vastly'' more effective if you also add a comment to explain why you care.
     
    5352 * '''Owned by''' says who is committed to taking the ticket forward.  We typically leave this field blank until we actively start working on it, lest others feel unable to work on a ticket because it is apparently owned, even though nothing is happening.
    5453
    55 == Remilestoning tickets after a release ==
     54== Re-milestoning tickets after a release ==
    5655
    5756When a release is made, any open tickets on that release's milestone will be moved to the next release's milestone.