Using SVN alone or in small workgroups - workflow approach?

Question

I spent several months working on a web application, and we got closer to the production stage. Soon the time will come to expand the development team with 1-3 people in this project.

I do not have much experience with SVN, but this is obviously the choice for most large companies, so I assume that SVN pros will undoubtedly outweigh the time spent fixing / checking ins / check outs, etc.

The workflow seems a bit more complicated with SVN, and even though I read Version Control with Subversion from O'Reilly Media, and I'm not sure if it overflows with using SVN for any reason other than backup when developing on my own or in a small (1-3 people) working group?

How do you do this? What is your version control workflow when working alone or in small workgroups?

Thank!

Answer 1

Like any SCM, it is definitely more than a backup.

• You can flag specific releases so that you can identify the point on all of your code that makes up the release.
• , . .
• SVN , .

SCM, . , .

? SCM.

• SCM (, Git), /. SVN , .
• /. , , . , , , .
• (, , TeamCity/Cruisecontrol/Hudosn), / , , /.
• .

Answer 2

, . , , , . "" , . , . , .

Answer 3

, . (DSCM), Mercurial, Git Bazaar. , , , , , .

Mercurial, , http://hginit.com/.

_{(source: hginit.com )}