DevelopmentRules

Jump to bottom Edit New page

Nar Chhantyal edited this page Sep 13, 2015 · 7 revisions

List of development rules and guidelines

Branch master is owned by release managers
- i.e. pull requests on master will be declined
development takes place on branch develop
- git-flow-alike we'll try to keep a running and most probably working code-base on master to prepare releases
- exchanging not-yet-finished features shall be done on feature branches, if we haven't created one that's needed, please file an issue / send a message / use smoke signal or bush telegraphy before applying a pull request ;)
- Send hotfix pull request for production/critical bugs to master branch
release managers decide what's merged from (our) develop to master
keep volatile or environment specific data or values out of repository
don't commit generated, cache or runtime created files
use .gitignore to prevent others from accidentally committing runtime files
PEP8 is mandatory