Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 7 and Version 8 of Developer/Bug_Reporting


Ignore:
Timestamp:
03/17/15 23:03:29 (9 years ago)
Author:
Wendell P Silva
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Developer/Bug_Reporting

    v7 v8  
    2121If you find a bug, but you are not fixing it (yet):
    2222
    23 # Create a (minimal) test-case.
    24 # Add the test-case to our test-suite, documenting it as a current failure unless the bug is a regression.
    25 # Add a bug report referencing the test-case to Trac.
     23  * Create a (minimal) test-case.
     24  * Add the test-case to our test-suite, documenting it as a current failure unless the bug is a regression.
     25  * Add a bug report referencing the test-case to Trac.
    2626
    2727If you want to provide additional information in the bug tracking system about a reported bug:
    2828
    29 # If the bug has been tracked down to a specific area or routine in RTEMS, please provide information about its location.
    30 # Minimize the test case.
    31 # Try the test case with earlier and later versions of RTEMS to determine which versions it affects and whether it is a regression. If it is a regression, identify the patch that introduced it.
     29  * If the bug has been tracked down to a specific area or routine in RTEMS, please provide information about its location.
     30  * Minimize the test case.
     31  * Try the test case with earlier and later versions of RTEMS to determine which versions it affects and whether it is a regression. If it is a regression, identify the patch that introduced it.
    3232
    3333If you fix a bug for which there is already a Trac entry:
    3434
    35 # Remove the failure notation on the test-case.
    36 # Attach your fix and test case to the Trac bug report.
    37 # Close the bug report in Trac.
     35  * Remove the failure notation on the test-case.
     36  * Attach your fix and test case to the Trac bug report.
     37  * Close the bug report in Trac.
    3838
    3939If you find a bug, and you are fixing it right then:
    4040
    41 # Create a (minimal) test-case.
    42 # Add the test-case to our test-suite, documenting it as known to work.
    43 # Check in your fixes.
     41  * Create a (minimal) test-case.
     42  * Add the test-case to our test-suite, documenting it as known to work.
     43  * Check in your fixes.
     44
    4445= Maintainer's View of Fields =
    4546
    … …  
    4748As a RTEMS-specific convention, we will attach a special meaning to some fields. The State field should be used in the following way:
    4849
    49  *  open - The PR has been filed and the responsible person(s) notified.
    50  *  analyzed - A maintainer has verified that this is indeed a bug in RTEMS. Every once in a while, old reports will need to be rechecked, to find out whether the bug still exists. At that time, an indication should be left in the report who tested the bug and when.
    51  *  feedback - The submitter was asked for further information, or asked to try out a patch. The PR remains in that state until the submitter responds.
    52  *  working - Someone is actively working on fixing the problem and has determined that it may take a while to fix. The intention of this state is to make sure that if someone is working on the problem, that everyone knows it so they can better coordinate efforts.
    53  *  suspended - Work on the problem has been postponed. This happens if a timely solution is not possible or is not cost-effective at the present time. The PR continues to exist, though a solution is not being actively sought. If the problem cannot be solved at all, it should be closed rather than suspended.
     50  *  '''open''' - The PR has been filed and the responsible person(s) notified.
     51  *  '''analyzed''' - A maintainer has verified that this is indeed a bug in RTEMS. Every once in a while, old reports will need to be rechecked, to find out whether the bug still exists. At that time, an indication should be left in the report who tested the bug and when.
     52  *  '''feedback''' - The submitter was asked for further information, or asked to try out a patch. The PR remains in that state until the submitter responds.
     53  *  '''working''' - Someone is actively working on fixing the problem and has determined that it may take a while to fix. The intention of this state is to make sure that if someone is working on the problem, that everyone knows it so they can better coordinate efforts.
     54  *  '''suspended''' - Work on the problem has been postponed. This happens if a timely solution is not possible or is not cost-effective at the present time. The PR continues to exist, though a solution is not being actively sought. If the problem cannot be solved at all, it should be closed rather than suspended.
    5455
    5556In addition, the high priority is reserved to maintainers in RTEMS, indicating that a certain problem must be solved before the next version of RTEMS is released.
     57
    5658= Procedures and Policies =
    5759