Changes between Version 1 and Version 2 of TicketLifeCycle


Ignore:
Timestamp:
Dec 1, 2007, 3:12:15 PM (12 years ago)
Author:
Alfonso Martínez de Lizarrondo
Comment:

typos

Legend:

Unmodified
Added
Removed
Modified
  • TicketLifeCycle

    v1 v2  
    1515== Confirming Bugs ==
    1616
    17 Someone from the core development team should them check the ticket information and decide whether it has enough useful information to move forward.
     17Someone from the core development team should then check the ticket information and decide whether it has enough useful information to move forward.
    1818
    1919The following actions could be taken when confirming a ticket:
     
    5757== Commit ==
    5858
    59 After a patch has been reviewed, someone with commit privileges in the source repository will commit it. The ticket is them resolved as "fixed", pointing to the relative changed with a message like "Fixed with [XYZ].".
     59After a patch has been reviewed, someone with commit privileges in the source repository will commit it. The ticket is then resolved as "fixed", pointing to the relative changed with a message like "Fixed with [XYZ].".
    6060
    6161----
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy