Git Workflow

Right git is super powerful and all, but it can be abused. I am by no means a git usage expert but here is the guidelines for git:

master should be the latest released stable build. Before 1.0 then it's just the latest stable build. No development should be done here.

I'm make a branch for each new feature I'm putting in. At the moment adding a new class is a new feature. However down the road it might become something more broad. So:
feature-xxxxx
should be the branch name. Once completed merge into master (if that starts to get hairy then I'll make a development branch, but not atm).

Fixing bugs should have the commit message "Fixes #xxx" where #xxx is the git issue number.If your bug fix is more than a few simple changes, then please make a branch for fixing the bug (issuefix-xxx as the branch name) and then when you merge it back, give the commit message as usual.