1.

0 Purpose

This document helps the team to understand the different steps in using SVN tool.

2.0 Scope

This procedure is applicable for all project teams during project life cycle.

3.0 Procedure

1. PM will raise the request to Netops team for creating a new SVN instance for the project.
2. Netops team will create a new SVN for project and give the admin access to PM.
Netops should create different roles with different access levels. E.g. read only... So anybody in read only
can only read the documents but not change it.
3. PM will have the permission to provide/control the access for team members
4. Project team will take the update every time before check in
5. Project team will branch off the main trunk code to develop new feature or fix the bugs assigned to them.
6. Once unit testing is passed, team will inform the project manager and commit the code with proper
comments.
7. PM will assign the resource to merge the code from all the branches and generate the build.
8. PM should ensure that team updates the proper comments for each commit (Check in and Check out).

4.0 References

1. Configuration Management Process

2. Release Management Process
3. Deployment Process

5.0 Definitions

Terms Definitions
Trunk The trunk is the main line of development in a SVN
repository
Branch A branch is a side-line of development created to make
larger, experimental or disrupting work without annoying
users of the trunk version. Also, branches can be used
to create development lines for multiple versions of the
same product, like having a place to backport bug fixes
into a stable release.
Tags tags are markers to highlight notable revisions in the
history of the repository

6.0 SVN folder structure