Changes between Version 1 and Version 2 of TicketProcessingGuide


Ignore:
Timestamp:
Jan 26, 2009, 9:52:25 PM (10 years ago)
Author:
stevenhl
Comment:

Update ticket close requirements

Legend:

Unmodified
Added
Removed
Modified
  • TicketProcessingGuide

    v1 v2  
    66This guide is written for both developers and reporters.
    77
    8 == New Tickets ==
     8== Entering New Tickets ==
    99
    10 When a new ticket is added, the milestone will default to the milestone
    11 corresponding to next scheduled ACPI version release.  As of 7/15/2008, this
    12 is ACPI version 3.11.
     10When a new ticket is created, the milestone will default to the milestone
     11corresponding to next scheduled ACPI version release.  As of 1/26/2009, this
     12is ACPI version 3.15.
    1313
    14 The version will default to current ACPI version (i.e. 3.10).
     14The version will default to current ACPI version (i.e. 3.15).
    1515
    1616These default values are defined by the ACPI project manager.
     
    1818When submitting a ticket, reporters should override these values if
    1919needed.
    20 Developers should correct these values as needed when responding to the ticket.
    2120
    2221A well written ticket will contain sufficient information so that the
     
    2423data.  Reporters should attempt to make this happen.
    2524
    26 == Responding to Tickets ==
     25== Handling New Tickets ==
    2726
    28 Developers should respond to a ticket within 1 or 2 working days.
     27Developers should review and respond to new tickets within 1 or 2 working days.
    2928As always, sooner is better.
    3029
     30When the ticket is reviewed, developers should change the ticket status to
     31assigned.
     32
     33Developers should correct the milestone and version fields, as needed.
     34
    3135If the reporter has neglected to supply the appropriate logs, the
    32 developer will point the reporter to
     36developer should point the reporter to
    3337http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
    3438http://ecomstation.ru/projects/acpitools/?action=logs.
     
    7276Tickets will only be be closed as resolved when the reported issue is
    7377fully resolved.
    74  A ticket is considered resolved when the reporter states that the issue no
    75 longer occurs.
    7678
    77 If the ticket resolution requires code changes, instruct the reporter to test
     79  * A ticket is considered resolved when the reporter states that the issue no longer occurs.
     80
     81When an ticket is resolved by code changes, the code changes must be
     82submitted to the Subversion respository before the ticket is closed.
     83
     84When an ticket is resolved by code changes, a comment must be added to the
     85ticket indicating the Subversion change set number.
     86
     87When an ticket is resolved by code changes, a comment must be added to the
     88ticket indicating the nature of the code change and how it resolved the
     89ticket issue.
     90
     91When an ticket is resolved by code changes, instruct the reporter to test
    7892the new version when it is released and move the ticket to the Feedback
    7993Pending milestone.
    80 
    81 When an ticket issue is corrected by code changes, it will be helpful the
    82 ticket should be updated to show the Subversion changeset number.  To be
    83 useful, this means that subversion commits should be done soon after the
    84 change is implemented.
    8594
    8695If a ticket will not be resolved by the new version release, leave the ticket