Commit Strategy
From SONIVIS:Wiki
| This article is work in progress. |
This article is about the commit strategy of SONIVIS. The main goal is to have a stable version at any time on trunk. Basically, we differentiate two roles: committers and contributors. Committers have the right to commit and change source code in the version control system, as opposed to contributors who are not allowed to modify source code.
Get commit rights
First of all you have to register at CodeBeamer (Website and the howto) . After that, please contact us and ask for commit permission. Please include a short motivation why you want to have commit rights.
Branching
For every code change there must be a task or bug entry in our task management system at CodeBeamer Trackers. Each entry has a unique number that should be used as name for the branch. Therefore every task should be reflected by it's own branch of all sonivis plugins (starting with de.sonivis.tool).
Tests
Merging to trunk
Merging a branch back to trunk is done by Benedikt. To trigger Benedikt, just set the status of the respective task in CodeBeamer to "resolved". No one else is allowed to check in merges to trunk!
