Changes between Version 2 and Version 3 of CheckinPolicy


Ignore:
Timestamp:
08/26/10 10:58:21 (4 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CheckinPolicy

    v2 v3  
    22 
    33=== Check-ins === 
    4  1. Work on the right branch - see VersionsAndBranching. 
     4 1. Work on the right branch - see BranchingPolicy. 
    55 1. Write tests for all changes. Unit tests go into ckan/tests/{area}/ and functional tests go into ckan/tests/functional/ . Tests describe intent and stop the code regressing in the future. 
    66 1. Run all the tests before you commit your code. It only takes 5 minutes! {{{nosetests ckan/tests}}} 
    … …  
    1414 * Send a link to the ticket to [CkanDiscuss ckan-discuss] and ask for suggestions. 
    1515 * Do it, whilst leaving the repo in a good state at all times (i.e. builds and works). Use another branch or bitbucket if necessary. 
    16  * Announce it on [CkanDiscuss ckan-discuss] and close the ticket when done. 
     16 * When done, close the ticket and announce it on [CkanDiscuss ckan-discuss]. 
    1717 
    1818=== Don't break the build ===