I've been told that most development shops have the following structure or at least close to this:
so:
ReponsitoryMain
Project1
branches
trunk
tags
Project2
...
So why is this better or best? What happens or what heartaches have you come across if you did it another way?
SVN is used to manage the current and previous versions of files like source code, documentation, and files. It acts as the time machine for the developers and allows them to go back and browse the history of the project.
A Subversion repository — abbreviated SVN repository — is a database filled with your code, files, and other project assets. A SVN repository maintains a complete history of every change ever made.
Most people do this because it's recommended by the Subversion book.
Here's a good explanation from the director of the CollabNet Subversion project:
http://blogs.collab.net/subversion/2007/04/subversion_repo/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With