Write and implement git policy document

[deni-zen]

I need to write a document outlining all of my git policies and processes. For instance...

• [x] Create wiki page for Git workflow document...
• [x] how do I branch and merge when it comes to development branches, version push branches (v0.1/master, v0.1/features-63, v1/master, beta/master, etc.).
• [x] Read up on the various common git workflows and decide on the best one for this particular project (keeping in mind you may eventually have additional developers).
• [ ] document how to branch and merge for feature additions, bug fixes, etc.
• [ ] how to associate a branch with a particular github issue #.
• [ ] Document best practices for git commit messages and include a default template to be used by developers working on the project. Etc. etc.
• [ ] Restructure git repository to conform to the new git workflow (whatever it may be)

[nozavroni]

This is a wonderful idea. And a great goal to have. Policy promotes consistency and limits confusion. But it's a stupid thing to hold back a release over. This will be an ongoing issue. Removing milestone.