Changes between Initial Version and Version 1 of TicketProcessingGuide


Ignore:
Timestamp:
Jul 15, 2008, 8:27:50 PM (16 years ago)
Author:
Steven Levine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketProcessingGuide

    v1 v1  
     1
     2[[PageOutline]]
     3
     4= ACPI Ticket Processing Guide =
     5
     6This guide is written for both developers and reporters.
     7
     8== New Tickets ==
     9
     10When a new ticket is added, the milestone will default to the milestone
     11corresponding to next scheduled ACPI version release.  As of 7/15/2008, this
     12is ACPI version 3.11.
     13
     14The version will default to current ACPI version (i.e. 3.10).
     15
     16These default values are defined by the ACPI project manager.
     17
     18When submitting a ticket, reporters should override these values if
     19needed.
     20Developers should correct these values as needed when responding to the ticket.
     21
     22A well written ticket will contain sufficient information so that the
     23developer can respond to the ticket without the need to request additional
     24data.  Reporters should attempt to make this happen.
     25
     26== Responding to Tickets ==
     27
     28Developers should respond to a ticket within 1 or 2 working days.
     29As always, sooner is better.
     30
     31If the reporter has neglected to supply the appropriate logs, the
     32developer will point the reporter to
     33http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
     34http://ecomstation.ru/projects/acpitools/?action=logs.
     35
     36== Displaying Tickets Requiring Developer Attention ==
     37
     38To display the list of the tickets that need attention, click on the roadmap link,
     39click on the current milestone and click on the open ticket count link.
     40
     41It is recommended that developers bookmark the resulting Custom Query.  This
     42will provide one-click access to this ticket list.
     43
     44The developers may choose to ignore tickets not displayed on this list.
     45
     46If a reporter believes a ticket has been incorrectly assigned, add a note to
     47the ticket explaining why.  This note will be seen by ACPI project
     48management.
     49
     50== Using the Feedback Milestone ==
     51
     52If the reporter fails to supply requested data in a reasonable period of time,
     53reassign the ticket to the [http://svn.netlabs.org/acpi/milestone/Feedback%20pending
     54Feedback Pending milestone].
     55
     56A reasonable period of time is probably 5 working days.  This helps avoid
     57cluttering up the list of tickets requiring developer attention with tickets
     58where the developer is waiting for the reporter.  It also generates ticket
     59e-mail to the reporter reminding the reporter that we are waiting for them.
     60
     61In general, once a ticket is moved to Feedback Pending milestone, it will be
     62ignored by the developers.
     63
     64== Responding to Tickets assigned to the Feedback Milestone ==
     65
     66If you are a reporter responding to a ticket assigned to the Feedback
     67milestone, try to remember to reassign the ticket to the current milestone.
     68This will help ensure that the developer is aware of the response.
     69
     70== When to Close Tickets ==
     71
     72Tickets will only be be closed as resolved when the reported issue is
     73fully resolved.
     74 A ticket is considered resolved when the reporter states that the issue no
     75longer occurs.
     76
     77If the ticket resolution requires code changes, instruct the reporter to test
     78the new version when it is released and move the ticket to the Feedback
     79Pending milestone.
     80
     81When an ticket issue is corrected by code changes, it will be helpful the
     82ticket should be updated to show the Subversion changeset number.  To be
     83useful, this means that subversion commits should be done soon after the
     84change is implemented.
     85
     86If a ticket will not be resolved by the new version release, leave the ticket
     87open.  If desired, move the ticket to a future milestone.  This will take
     88the ticket off the list of tickets requiring developer attention for the
     89current milestone.
     90
     91== Maintaining Tickets After a New Release ==
     92
     93When a new version is released and the milestone corresponding to the new
     94version is be marked complete, there will usually still be open tickets for
     95the milestone.  Any remaining open tickets will automatically be moved to
     96the next milestone.
     97
     98== Handling Stale Tickets ==
     99
     100Over time, stale tickets will accumulate in the Feedback Pending milestone.
     101The ACPI project manager will monitor this milestone and determine how to
     102dispose of these tickets.
     103