Changes between Version 14 and Version 15 of HowToContribute

Show
Ignore:
Timestamp:
08/24/07 06:31:35 (6 years ago)
Author:
crschmidt
Comment:

rearrange

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v14 v15  
    3737    1. Will not cause a dispute in the community -- if there is reason to believe that the change might be controversial, the ticket and patch should be submitted to the SteeringCommittee for a vote. 
    3838  * We consider the act of committing code to the repository to be implicit acceptance of the project's published procedures. 
    39   * When committing code changes, include the ticket number that the commit is designed to resolve in the commit message, for future tracking. Code changes should not be made without a corresponding ticket. Trac will automatically pick up on messages with text in a specific format, to help you manage tickets from commit messages. Including text of the form: 
     39  * Commit messages should be informative, and should mention any author of the patch if the author is not the committer. 
     40  * When committing code changes, include the ticket number that the commit is designed to resolve in the commit message, for future tracking. Code  
     41changes should not be made without a corresponding ticket. Trac will automatically pick up on messages with text in a specific format, to help you manage tickets from commit messages. Including text of the form: 
    4042    * (Closes #925.) -- Closes the ticket (with the revision number and commit message added as a comment). 
    4143    * (References #925.) -- Adds a comment to the ticket with the commit message. 
    42   * Commit messages should be informative, and should mention any author of the patch if the author is not the committer. 
    4344  * If the patch is from a new contributor, ensure that the user has sent in a [wiki:CLA] before committing and add the contributor's name to doc/authors.txt when committing.