Source / version control methodology

Question

we are finally decided to switch from sourcesafe (the devil) to svn. as we are a startup company we still 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 ?

possible duplicate of [Source Control - If, Why, How to start?](http://stackoverflow.com/questions/2064250/source-control-if-why-how-to-start) — gbjbaanb, Mar 09 '11 at 13:55

score 2 · Answer 1 · edited May 23 '17 at 12:04

2

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

Also, a link to the Subversion Manual.

edited May 23 '17 at 12:04

Community

1
1

answered Mar 08 '11 at 21:43

bentsai

3,063
1
27
29

score 1 · Accepted Answer · edited May 23 '17 at 11:55

1

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.

edited May 23 '17 at 11:55

Community

1
1

answered Mar 08 '11 at 21:40

VonC

1,262,500
529
4,410
5,250

I wonder why you haven't recommended [git](http://stackoverflow.com/questions/2064250/source-control-if-why-how-to-start/2064294#2064294) here... – Tobias Kienzler Mar 09 '11 at 13:40
@Tobias: because the OP mentions SVN in the question (at least in the tags) – VonC Mar 09 '11 at 13:51
1

fair enough. I just thought it might be worth mentioning the additional backup mechanism implicitly given by a distributed system (which shouldn't lead to carelessness though) – Tobias Kienzler Mar 09 '11 at 13:54
@Tobias: true, provided to not go too far ;) http://stackoverflow.com/questions/2576198/git-as-a-backup-and-version-control-system – VonC Mar 09 '11 at 14:01
good point and interesting read... what's your opinion of [bup](https://github.com/apenwarr/bup) then? – Tobias Kienzler Mar 09 '11 at 15:54

score 1 · Answer 3 · edited Mar 09 '11 at 13:37

1

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!

edited Mar 09 '11 at 13:37

Stefan

43,293
10
75
117

answered Mar 08 '11 at 21:46

Matt

1,265
1
16
24

Source / version control methodology

3 Answers3