Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 ?
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.