Changes between Version 5 and Version 6 of Developer/Bug_Reporting


Ignore:
Timestamp:
Mar 17, 2015, 10:46:58 PM (5 years ago)
Author:
Wendell P Silva
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Bug_Reporting

    v5 v6  
    1 = RTEMS Bugzilla =
     1= RTEMS Bug Reporting =
    22
    33
     
    66
    77
    8 Our preferred way of receiving bug reports is via the [http://www.rtems.org/bugzilla RTEMS Bugzilla] bug reporting system. For posting patches not specifically related to bugs, we prefer to use the [wiki:TBR/Website/RTEMSMailingLists Developer's Mailing List].
     8Our preferred way of receiving bug reports is via the [http://devel.rtems.org RTEMS Trac] bug reporting system. For posting patches not specifically related to bugs, we prefer to use the [wiki:TBR/Website/RTEMSMailingLists Developer's Mailing List].
    99
    10 TODO: add instructions for submitting bugs through the bugzilla interface. Redirect external links to the bugzilla to this page.
     10In general, if you have a bug to submit follow the instructions:
     11  1. Sign in Trac website
     12  2. Click in My Tickets (right upper corner of the screen)
     13  3. Search for a similar bug (to avoid duplicates)
     14  4. Describe the bug, attach evidences, add detailed instructions in order to reproduce the bug and save it.
    1115
    12 = Managing Bugs (Bugzilla and the test-suite) =
     16= Managing Bugs =
    1317
    1418
     
    1923# Create a (minimal) test-case.
    2024# Add the test-case to our test-suite, documenting it as a current failure unless the bug is a regression.
    21 # Add a bug report referencing the test-case to Bugzila.
     25# Add a bug report referencing the test-case to Trac.
    2226
    2327If you want to provide additional information in the bug tracking system about a reported bug:
     
    2731# 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.
    2832
    29 If you fix a bug for which there is already a Bugzila entry:
     33If you fix a bug for which there is already a Trac entry:
    3034
    3135# Remove the failure notation on the test-case.
    32 # Attach your fix and test case to the Bugzilla bug report.
    33 # Close the bug report in Bugzila.
     36# Attach your fix and test case to the Trac bug report.
     37# Close the bug report in Trac.
    3438
    3539If you find a bug, and you are fixing it right then: