Version Control

Use the following strategies for version control:

  1. Do continuous integration.
  2. Use toggle feature on/off so that application is configurable to a certain extent, so that features can be turned off on at run time or build time. This helps even if new code is added to the main branch but still can be turned off with ease.
  3. Use of De-centralized VCS like Git or Mecurial. SVN is a Centralized VCS. In De-VCS , each person has a copy of the repository and can be shared with individual team members without touching the central repository.

SVN

Use the TRUNK and when you are ready create a TAG.
Always update before making the changes and commit after making the changes. Check in and Checkout must always be done only once per source machine.

Individual:
ADD- Adds a new file to the repository and commits it.
Commit – Commits the new changes of the file to the repository.

Team:
Create a branch out of a trunk. Work on the branch as an Individual, then when done, merge the changes to Trunk.

Tools:
http://subclipse.tigris.org/update_1.8.x – Eclipse Update Site
Tortoise
Command Line

Commands:
svn list svn://xyz/repo will list the repository contents
svn mkdir svn://xyz/repo/dir_name -m “message” – creates dir_name directory under the repository
svn co svn://xyz/repo/dir_name – checkout the new directory you just created.
cd dir_name
Make changes in this directory – create files/folders etc.
svn add some_dir – adds any new files/folders but you don’t see them in svn repo until you commit it
svn commit -m “message” – commits the latest changes to the svn

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s