Source / version control methodology

we are finally decided to switch from sourcesafe (the devil) to svn. as we are a startup company we still 开发者_JAVA百科have no idea of the best (not worst) way to save our code. i have read about some ways others do that. can any one give me a link to a good explanation for a source control methodology. thank you.

update: using the software is nice and helpful. but we need to learn the methodology of how to save the code (branching trunk and tagging) how do you do it ?

---

See the answers here for this SO question and this related question.

Also, a link to the Subversion Manual.

---

There is a difference between "backup" (as in "saving our code") and "versioning" (as in "saving a point in time of our code").
And there is a difference between saving it locally, or exporting that to a third-party provider (which, for private code might be problematic).

In other words, once you have begun to version you code, you will need to backup regularly your SVN repo (and test your backup ;) ), but those are two different operations.

---

I have used TortoiseSVN for multiple projects. It's free, easy to use and does everything SVN should do.

TortoiseSVN's link

Here is a good tutorial to getting everything going using Tortoise.

Tortoise Tutorial

Enjoy and best of luck!