Subversion
CTRNet uses Subversion for code management and version control. All repositories are hosted with CVSDude to ensure maximum repository availability.
This wikipage will not cover in-depth usage of our repositories. For more information please refer to the many online resources and tutorials. A great place to start is the Subversion reference book, available online for free here
Contents |
Recommended Clients
- TortiseSVN - Integrates with Windows Explorer. Highly recommended.
- Subclipse - Subversion plugin for Eclipse.
- SlikSVN - Command line client/server for Windows (x32/x64)
Accessing Repositories
For those who wish to checkout the latest working copy revision for development purposes use this link:
https://ctrnet.svn.cvsdude.com/atim2/trunk
Connecting your DAV drive to SVN
Development Environment and Workflow for CTRNet Developers
In general, here is a recommended workflow for those developers working on the ATiM application:
Repository Layout
Each repository (ATiM, MDR, Core) has the following structure:
- /<project_name>/branches - Contains feature branches which are eventually merged back into the trunk or major release branches which are supported over time.
- /<project_name>/tags - 'Snapshots' of the repository taken at a particular point in time. Each major/minor release will have a tag.
- /<project_name>/trunk - Tracks the main development line. Checkout of the trunk will give you the latest development release.
ATiM/MDR have an additional folder. /vendor is used for tracking the core version used within each application. When a new core release occurs the /vendor/current is updated with this new release and tagged. Then, the new changes can be merged with customizations made to the core for each application.
For those developers releasing new version of the core please see the wiki page Releasing New Core Versions for a step-by-step SVN process.
