Changes between Version 1 and Version 2 of trac_usage


Ignore:
Timestamp:
Sep 2, 2006, 4:32:42 AM (15 years ago)
Author:
Peter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • trac_usage

    v1 v2  
    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.
    1212
    13  * Until trac supports ticket dependencies we must keep track of them ourselves. Add links to know dependencies in the ticket desciption field. The order of the dependecies should reflect the order in which the tickets should be resolved.
     13 * Until trac supports ticket dependencies we must keep track of them ourselves. Add links to known dependencies in the ticket description field. The order of the dependecies should reflect the order in which the tickets should be resolved.
    1414
    15  * The commits to the repository should be as small as possible,''Commit often and do it minimalistic''. If there is a need to make large changes before a proper commit can be made (remember, the code in the repository must always compile) a branch should be created.
     15 * The commits to the repository should be as small as possible, ''Commit often and do it minimalistic''. If there is a need to make large changes before a proper commit can be made (remember, the code in the repository must always compile) a branch should be created.
    1616
    1717 * Use the ticketing system for discussions about tickets.