21
edits
Changes
no edit summary
</pre></big>
==== Branches ====
* '''Branches''' is a common place for all team members' workspaces.
* Each team member should create a home directory or '''workspace''' (member-id1, member-id2,...) for his own development tasks in branches.
* The team-member's workspace is then divided in several directories (workspaces) during the development of the project. These workspaces(Task1, Task2, ...) are usually copies of the '''trunk''' to be worked on.
*: ''These directories(Task1, Task2,...) are called branches of trunk. Also Note that when the word '''branch''' is used as a verb, it means copying the whole trunk into a subdirectory, either in '''Branches''' or '''tags'''.
==== Tags ====
* '''tags''' directory holds '''copies''' of successful stages of '''trunk''' during development. (''Also called as '''Milestones''''')
* '''tags''' are never modified or edited. ''You may branch the a directory of tag into branches under a workspace and then modify it and apply the changes back to trunk, but the contents of a tag should never change''
** When a release is due, always the latest version of that realease will be marked.
**: ''If R0.3 is due, and in '''tags''' R0.3, R0.31, R0.32 are present, then R0.32 will be marked
==== Trunk ====
* '''trunk''' IS the project at current staged, '''complied and run-able'''
* '''trunk''' should never be at a non-complied stage. (usually trunk should be the exact copy as (or better than) the last version in tags).
* If only one project is done within this repository, then trunk has no project level subdirectory and is the root of the project, otherwise, trunk is divided into several directories for each project to be version-controlled.
*: ''In this case Tags should also be divided to the exact same project directories as trunk''
== Starting the Project On SVN ==
