SVN : Sub Version Repositories.. How to effectively work as a team
Sub Versions are a nice way to manage and Edit a Project as a team. An SVN repository contains the complete code which is to be managed and different people have different rights on accessing and changing the code.
These SubVersions consist of various check points when the code was in a commit state and we can edit these versions or rollback to the previous stable versions and work on them. Hence these repositories help us in managing the code effectively in case a wrong commit is made to the code at any stage.
The commit operations can only be done by authorized people who have access rights on committing a particular file of the project. Read and Write Access can be file as well as project specific.
SVN are pretty common in Unix as well as Windows based machines ( Tortoise SVN ).
EDIT : GIT IS WAY MORE COOLER! FORGET ABOUT THIS!
These SubVersions consist of various check points when the code was in a commit state and we can edit these versions or rollback to the previous stable versions and work on them. Hence these repositories help us in managing the code effectively in case a wrong commit is made to the code at any stage.
The commit operations can only be done by authorized people who have access rights on committing a particular file of the project. Read and Write Access can be file as well as project specific.
SVN are pretty common in Unix as well as Windows based machines ( Tortoise SVN ).
EDIT : GIT IS WAY MORE COOLER! FORGET ABOUT THIS!