Development workflow
The following guidelines describe the development workflow of the Decision Architect:
- Code Documentation: Each method/function/class should have a short statement about its purpose, e.g. What does it do?
- Whenever you make a significant change to a source code file, add your name to the list of contributors. A significant change can be a bug fix, a refactoring, or adding new methods.
- Each developer/team should work on his/their own branch.
- Branches should be regularly merged with the master branch, preferably once a week on Friday. The developer who wants to pushes his changes to the master, should make sure that the new feature has been checked by one of the coordinators.
- All changes to the source code should have a corresponding item in the issue list on Codeplex.
- For each found bug, an issue is created on Codeplex in the ‘issues’ tab
Branching
The following instructions describe the branching process.
- Right click on the folder you want to branch in the Source Control Explorer of Visual Studio
- Click on Branching and Merging > Branch...
- In this window several options can be set:
- The version which needs to be branched. Latest Version is the version on CodePlex.
- The Target Branch Name. This name should be of the form: $/da/[folder name that is branched]-[name of the branch]. So a branch for the Forces Viewpoint will look like "$/da/src-ForcesViewpoint".
- The Description can be used for filling in the purpose of the branch.
- Click on Branch.
- The next window will ask for a confirmation and you must click on yes.
- The new branch is created and you can start coding if you open the solution file in the branch!