-
Notifications
You must be signed in to change notification settings - Fork 15
Best practices
egelmex edited this page Apr 24, 2013
·
3 revisions
This page will list best practices for the project. Sometimes this rules won't work, sometimes we will need to update them, but they should lead to better code and make it easier for others to work with us.
- Always work in your own branch/fork.
- One feature/bug fix per commit.
- Commits will have useful commit messages in the standard git format.
- Commits with bad commit messages should not be pulled.
- Make a pull request for each change set.
- Commits should be reviewed by another member of the team before being pulled into master.
- Bug fixes should be cherry-picked into stable branch.
- master should always be stable.
- Releases will be tagged in form Major.Minor.Revision
- Each Minor version will have it's own branch.
- No backwards compatibility breaking could should be pulled into a Minor branch.
- Minor should be bumped if we break backwards compatibility, and a stable branch should be made.
- Packages should be based off a tag.