| | 1 | = Chimera 2 Revision Control = |
| | 2 | |
| | 3 | We will use '''git''' and '''git flow''' for revision control to manage Chimera 2 source code. Development will follow the [http://nvie.com/posts/a-successful-git-branching-model/ Vincent Driessen's branching model] where the '''master''' branch is the release branch and the '''develop''' branch is the daily build branch. The remainder of this document describes some common tasks using '''git'''. |
| | 4 | |
| | 5 | [[PageOutline]] |
| | 6 | |
| | 7 | == Create Team Repository == |
| | 8 | == Create Developer Repository on plato == |
| | 9 | == Use '''develop''' Branch Directly for Development == |
| | 10 | == Use Feature Branch for Development == |
| | 11 | == Stash Modified Files before Switching Branches == |
| | 12 | == Create Remote Repository == |
| | 13 | == Use plato Repository to Coordinate Development on Multiple Hosts == |