Repository Layout for group of projects.In the following examples, the projects calculator, calculator and spreadsheet are using repository directory as their root then each project has its own 3 subdirectories. In this layout, main repository directory is used as project root. Repository layout for non-grouped projects.In future, tags are used to create branches from that point.
#Projectlocker smartsvn code#
at what point code are released for production or acceptance testing. Tags are used to remember the last release point i.e. We should also try to synchronize mainline code to branches on almost daily basis because that way branches code will remain up-to-date with respect to mainline code. Because each active branch costs in complexity and administration. We should create branches only when it is necessary otherwise we should avoid it.
Because if we do short-time fixes (bugs & validation) along long term changes (continuous development) on main-line code then it will be very difficult to release short-time fixes. The branches are used to separate different life cycle of development. This directory mostly contains bug free and updated code.
Trunk is a directory where mainline of development is done. The topmost directory that contains data related to that project and Subversion usually create three types of sub directories inside the respective project directory. In most cases, main repository directory is used as project root. Subversion allows using different type of repository layouts for directory hierarchies.