Changes between Version 3 and Version 4 of TicketProcessingGuide


Ignore:
Timestamp:
Feb 9, 2009, 9:14:24 PM (9 years ago)
Author:
stevenhl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketProcessingGuide

    v3 v4  
    1111
    1212When a new ticket is created, the milestone will default to the milestone
    13 corresponding to next scheduled ACPI version release.  As of 1/26/2009, this
     13corresponding to next scheduled ACPI version release.  As of 2/9/2009, this
    1414is ACPI version 3.15.
    1515
    16 The version will default to current ACPI version (i.e. 3.15).
     16The version will default to the current ACPI version. As of 2/9/2009, this is ACPI version 3.14. If you are reporting an issue for some other ACPI release, please override the default with the correct version.
    1717
    18 These default values are defined by the ACPI project manager.
    19 
    20 When submitting a ticket, reporters should override these values if needed.
     18The default values are defined by the ACPI project manager.
    2119
    2220A well written ticket will contain sufficient information so that the
    2321developer can respond to the ticket without the need to request additional
    24 data.  Reporters should attempt to make this happen.
    25 http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
     22data.  http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
    2623http://ecomstation.ru/projects/acpitools/?action=logs
    2724will help you understand how to make this happen.
     
    2926=== Responding to Tickets assigned to the Feedback Milestone ===
    3027
    31 If your ticket has been moved to the Feedback Pending milestone, the developer needs you to take some action.
     28If your ticket has been moved to the Feedback Pending milestone, the developers need you to supply additional data or take some action.
    3229It is your responsibility to do this and respond the the ticket.
    33 When you respond to the ticket, try to remember to reassign the ticket to the current milestone.
    34 This will help ensure that the developer is aware of your response.
     30When you respond to the ticket, it is also your responsibility to reassign the ticket to the current milestone.
     31This will ensure that the developers are aware that you have responded.
    3532
    36 If you questions of any kind about the status of your ticket, add a note to the ticket.
     33If you forget to reassign the ticket, there may be a delay until the developers realizes you have responded.
     34Developers must give priority to tickets assigned the the current milestone and may or may not notice your response if you neglect to reassign the ticket to the current milestone.
     35
     36If you have questions of any kind about the status of your ticket, add a note to the ticket.
    3737This note will be seen by ACPI project management.
    3838
     
    4949
    5050If the reporter has neglected to supply the appropriate logs, the
    51 developer should point the reporter to
     51developers should point the reporter to
    5252http://svn.netlabs.org/acpi/wiki/WikiStart#SubmittingTickets and
    5353http://ecomstation.ru/projects/acpitools/?action=logs and
     
    5555Feedback Pending milestone].
    5656
    57 If 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
     57If the developers need 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
    5858Feedback Pending milestone].
    5959
    60 === Displaying Tickets Requiring Developer Attention ===
     60=== Displaying Tickets Requiring Developers Attention ===
    6161
    62 To display the list of the tickets that need attention, click on the roadmap link,
     62To display the list of the tickets that need attention, click on the [[http://svn.netlabs.org/acpi/roadmap roadmap]] link,
    6363click on the current milestone and click on the open ticket count link.
    6464
     
    7474out of the developers current work list.
    7575
    76 In general, once a ticket is moved to Feedback Pending milestone, the developer should
    77 ignore the ticket until the reporter to supplies the requested information.
     76In general, once a ticket is moved to Feedback Pending milestone, the developers should
     77ignore the ticket until the reporter to supplies the requested information and reassigns the ticket to the current milestone.
    7878
    7979=== When to Close Tickets ===
    8080
    81 Tickets will only be be closed as resolved when the reported issue is
    82 fully resolved.
     81Tickets will only be be closed as resolved when the reported issue is fully resolved.
    8382
    84   * A ticket is considered resolved only when the reporter states that the issue no longer occurs.
     83'''A ticket is considered resolved only when the reporter states that the issue no longer exists.'''
    8584
    86 When an ticket is resolved by code changes, the code changes must be
    87 submitted to the Subversion repository before the ticket is closed.
     85When the resolution requires no code changes, the ticket may be marked closed when the reporter indicates that the issue has been resolved.
    8886
    89 When an ticket is resolved by code changes, a comment must be added to the
    90 ticket indicating the Subversion change set number.
     87When the resolution requires source code changes, the code changes must be
     88submitted to the Subversion repository as soon as possible after the reporter indicates the issues is resolved.
     89In general, the changes should be submitted within one or two business days.  This allows times for source code and comments to be cleaned up, if needed.
    9190
    92 When an ticket is resolved by code changes, a comment must be added to the
    93 ticket indicating the nature of the code change and how it resolved the
    94 reported issue.
     91After the changeset is submitted, a comment must be added to the ticket indicating the Subversion change set number along with a description of the nature of the code change and how it resolved the reported issue.
    9592
    96 When an ticket is resolved by code changes, instruct the reporter to test
    97 the new version when it is released and move the ticket to the Feedback
    98 Pending milestone.
     93When the resolution requires source code changes, instruct the reporter to test the next milestone version when it is released and move the ticket to the Feedback Pending milestone.
    9994
    100 The 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.
     95'''The above means that the test results for interim builds will never cause a ticket to be closed.  Only the test results for a milestone release version will cause a ticket to be closed.'''
    10196
    102 If a ticket will not or can not be resolved by the new version release, leave the ticket
    103 open.  If desired, move the ticket to a future milestone.  This will take
    104 the ticket off the list of tickets requiring developer attention for the
    105 current milestone.
     97If a ticket will not or can not be resolved by the next milestone release, leave the ticket open.
     98If the developers wish to take this ticket off the list of tickets requiring developer attention for the
     99current milestone, move the ticket to a future milestone.
    106100
    107101== Management ==