Changes between Version 3 and Version 4 of CheckinPolicy


Ignore:
Timestamp:
02/10/11 13:52:42 (3 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CheckinPolicy

    v3 v4  
    44 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. 
    6  1. Run all the tests before you commit your code. It only takes 5 minutes! {{{nosetests ckan/tests}}} 
     6 1. Run all the tests before you commit your code. It only takes 5 minutes! {{{nosetests --ckan ckan/tests}}} 
    77 
    88=== Starting out === 
    9  * Before you can commit changes to the OKF repo, you'll need access rights - ask for these on [CkanDiscuss ckan-discuss]. 
     9 * Before you can commit changes to the OKF repo, you'll need access rights - ask for these on [CkanDev ckan-dev]. 
    1010 
    1111=== Life-cycle of a change === 
    … …  
    1818=== Don't break the build === 
    1919 * Keep an eye on [http://buildbot.okfn.org/waterfall buildbot] to make sure you don't break the build. If you're a regular developer, ask to be added to the buildbot emails. Don't wait to be nagged by other frustrated developers ;-) 
    20  * If you break the build, please fix it quickly. If it may take time then email [CkanDiscuss ckan-discuss] to let others know what the plan is. 
     20 * If you break the build, please fix it quickly. If it may take time then email [CkanDev ckan-dev] to let others know what the plan is.