Changes between Version 1 and Version 2 of GCI/QA/InvestigateTicket


Ignore:
Timestamp:
Nov 29, 2015, 10:50:31 PM (4 years ago)
Author:
Gedare Bloom
Comment:

Import instructions.

Legend:

Unmodified
Added
Removed
Modified
  • GCI/QA/InvestigateTicket

    v1 v2  
    77
    88=== Directions for Students ===
     9
     10{{{#!comment
    911Look through [https://devel.rtems.org/query?status=accepted&status=assigned&status=new&status=reopened&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority open tickets] and investigate an open ticket to propose a way forward to close it. Add your findings to the table below.
     12}}}
     13
     14 Before taking and attempting this task, you should first complete a HelloWorld task.
     15
     16 You should have been given a ticket number for a specific ticket (bug) to investigate.
     17 If the bug has no existing test case then implement a new test case
     18 within an appropriate subdirectory of testsuites and submit the patches
     19 to the ticket on Trac. If the bug affects functionality that is already
     20 tested by an existing test case, then extend that test case to check for the
     21 conditions of the reported bug (if the test for the bug does not exist).
     22
     23 If the bug has already been fixed make a comment on the ticket to that effect.
     24
     25 If the bug has a fix you can implement, then write the fix and attach any
     26 patches to the ticket on RTEMS Trac.
     27
     28 If the bug is not fixed and is beyond your abilities, then write a brief report
     29 describing the bug behavior and possible fixes. Submit the report as a comment
     30 on the ticket.
     31
     32 Fill in an entry to the table below with the ticket you investigated, and any follow-up needed.
    1033
    1134=== PRs Addressed in GCI2015 ===