Changes between Version 8 and Version 9 of trac_usage


Ignore:
Timestamp:
Feb 21, 2008, 8:34:15 PM (14 years ago)
Author:
Markus Ringnér
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • trac_usage

    v8 v9  
    77 * Prefer smaller tickets. A ticket may cover many aspects early in the process going from an idea or a request to implementation. The goal is to split larger tickets into smaller that represent well defined tasks.
    88
    9  * A ticket must be well specified. This implies that the creator of a ticket must supply information such that another developer can perform the task. Too little information may disqualify other developer from resolving the issue.
     9 * A ticket must be well specified. This implies that the creator of a ticket must supply information such that another developer can perform the task. Too little information may disqualify other developers from resolving the issue.
    1010
    1111 * When a developer starts to fix a ticket the ticket must be accepted. This is important to make sure that no one else is working on the same issue. Until a ticket is assigned to someone it is free for anyone to claim, but one should only claim tickets that will be solved in reasonable time.