Changes between Version 2 and Version 3 of TicketProcessingGuide


Ignore:
Timestamp:
Feb 9, 2009, 7:25:47 PM (16 years ago)
Author:
Steven Levine
Comment:

Reorganize by roles

Legend:

Unmodified
Added
Removed
Modified

  • TicketProcessingGuide

    v2 v3  
    44= ACPI Ticket Processing Guide =
    55
    6 This guide is written for both developers and reporters.
     6This guide is written for reporters, developers and ACPI project management.
    77
    8 == Entering New Tickets ==
     8== Reporters ==
     9
     10=== Entering New Tickets ===
    911
    1012When a new ticket is created, the milestone will default to the milestone
    … …  
    1618These default values are defined by the ACPI project manager.
    1719
    18 When submitting a ticket, reporters should override these values if
    19 needed.
     20When submitting a ticket, reporters should override these values if needed.
    2021
    2122A well written ticket will contain sufficient information so that the
    2223developer can respond to the ticket without the need to request additional
    2324data.  Reporters should attempt to make this happen.
     25http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
     26http://ecomstation.ru/projects/acpitools/?action=logs
     27will help you understand how to make this happen.
    2428
    25 == Handling New Tickets ==
     29=== Responding to Tickets assigned to the Feedback Milestone ===
     30
     31If your ticket has been moved to the Feedback Pending milestone, the developer needs you to take some action.
     32It is your responsibility to do this and respond the the ticket.
     33When you respond to the ticket, try to remember to reassign the ticket to the current milestone.
     34This will help ensure that the developer is aware of your response.
     35
     36If you questions of any kind about the status of your ticket, add a note to the ticket.
     37This note will be seen by ACPI project management.
     38
     39== Developers ==
     40
     41=== Handling New Tickets ===
    2642
    2743Developers should review and respond to new tickets within 1 or 2 working days.
    2844As always, sooner is better.
    2945
    30 When the ticket is reviewed, developers should change the ticket status to
    31 assigned.
     46When the ticket is reviewed, developers should change the ticket status to assigned.
    3247
    3348Developers should correct the milestone and version fields, as needed.
    … …  
    3651developer should point the reporter to
    3752http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
    38 http://ecomstation.ru/projects/acpitools/?action=logs.
     53http://ecomstation.ru/projects/acpitools/?action=logs and
     54move the ticket to the [http://svn.netlabs.org/acpi/milestone/Feedback%20pending
     55Feedback Pending milestone].
    3956
    40 == Displaying Tickets Requiring Developer Attention ==
     57If the developer needed additional information from the reporter, add a note the the ticket and move the ticket to the [http://svn.netlabs.org/acpi/milestone/Feedback%20pending
     58Feedback Pending milestone].
     59
     60=== Displaying Tickets Requiring Developer Attention ===
    4161
    4262To display the list of the tickets that need attention, click on the roadmap link,
    … …  
    4666will provide one-click access to this ticket list.
    4767
    48 The developers may choose to ignore tickets not displayed on this list.
     68In general, developers should ignore tickets not displayed on this list.
    4969
    50 If a reporter believes a ticket has been incorrectly assigned, add a note to
    51 the ticket explaining why.  This note will be seen by ACPI project
    52 management.
     70=== Using the Feedback Pending Milestone ===
    5371
    54 == Using the Feedback Milestone ==
     72The purpose of the [http://svn.netlabs.org/acpi/milestone/Feedback%20pending
     73Feedback Pending milestone] is that tickets that are awaiting a response from the reporter
     74out of the developers current work list.
    5575
    56 If the reporter fails to supply requested data in a reasonable period of time,
    57 reassign the ticket to the [http://svn.netlabs.org/acpi/milestone/Feedback%20pending
    58 Feedback Pending milestone].
     76In general, once a ticket is moved to Feedback Pending milestone, the developer should
     77ignore the ticket until the reporter to supplies the requested information.
    5978
    60 A reasonable period of time is probably 5 working days.  This helps avoid
    61 cluttering up the list of tickets requiring developer attention with tickets
    62 where the developer is waiting for the reporter.  It also generates ticket
    63 e-mail to the reporter reminding the reporter that we are waiting for them.
    64 
    65 In general, once a ticket is moved to Feedback Pending milestone, it will be
    66 ignored by the developers.
    67 
    68 == Responding to Tickets assigned to the Feedback Milestone ==
    69 
    70 If you are a reporter responding to a ticket assigned to the Feedback
    71 milestone, try to remember to reassign the ticket to the current milestone.
    72 This will help ensure that the developer is aware of the response.
    73 
    74 == When to Close Tickets ==
     79=== When to Close Tickets ===
    7580
    7681Tickets will only be be closed as resolved when the reported issue is
    7782fully resolved.
    7883
    79   * A ticket is considered resolved when the reporter states that the issue no longer occurs.
     84  * A ticket is considered resolved only when the reporter states that the issue no longer occurs.
    8085
    8186When an ticket is resolved by code changes, the code changes must be
    82 submitted to the Subversion respository before the ticket is closed.
     87submitted to the Subversion repository before the ticket is closed.
    8388
    8489When an ticket is resolved by code changes, a comment must be added to the
    … …  
    8792When an ticket is resolved by code changes, a comment must be added to the
    8893ticket indicating the nature of the code change and how it resolved the
    89 ticket issue.
     94reported issue.
    9095
    9196When an ticket is resolved by code changes, instruct the reporter to test
    … …  
    9398Pending milestone.
    9499
    95 If a ticket will not be resolved by the new version release, leave the ticket
     100The above means that the test results for an interim build will never cause a ticket to be closed.  Only the test results for a released version will cause a ticket to be closed.
     101
     102If a ticket will not or can not be resolved by the new version release, leave the ticket
    96103open.  If desired, move the ticket to a future milestone.  This will take
    97104the ticket off the list of tickets requiring developer attention for the
    98105current milestone.
    99106
    100 == Maintaining Tickets After a New Release ==
     107== Management ==
     108
     109=== Maintaining Tickets After a New Release ===
    101110
    102111When a new version is released and the milestone corresponding to the new
    103 version is be marked complete, there will usually still be open tickets for
    104 the milestone.  Any remaining open tickets will automatically be moved to
     112version is be marked complete, there will usually still be open tickets assigned to
     113the milestone.  The ACPI project manager will move these open tickets to
    105114the next milestone.
    106115
    107 == Handling Stale Tickets ==
     116=== Handling Stale Tickets ===
    108117
    109 Over time, stale tickets will accumulate in the Feedback Pending milestone.
     118Over time, stale tickets may accumulate in the Feedback Pending milestone.
    110119The ACPI project manager will monitor this milestone and determine how to
    111120dispose of these tickets.