How we are using subversion
I mentioned that I have just spent some time importing all our projects at work into the new SVN repository, so I thought I’d try to explain how we have setup up the repository, and how we plan to do development.
We have had one repository setup where all our projects are going to be held. The structure of our repository looks like the following.
repository
– projectname
—- branches
——– projectname_releasenumber
—- tags
——– projectname_releasenumber
—- webroot (trunk)
——– projectname
The way our team has agreed to work is as follows:
- The webroot (trunk) will always be a mirror of what is currently in production.
- For any new releases a branch must be created based off the trunk.
- Developers will do their work in the branch.
- The test, acceptance and finally the production release will all be from the branch.
- After the production deployment has been signed off the branch will be merged and sync’d to the trunk.
- Create a tag for the new release.
- Rinse and repeat!
Is that roughly how others handle version control?
About this entry
You’re currently reading “How we are using subversion,” an entry on ConstantConfusion
- Published:
- 06.20.08 / 2pm
- Category:
- ColdFusion, Development

No comments
Jump to comment form | comments rss [?] | trackback uri [?]