Question Details

Browse

Bzr vs CVS vs Subversion

By Marty Bennett - Oct. 02, 2007

Hi - I am looking for a source control system to use for our outsourced development team. We are currently using Microsoft Visual Source Safe and I have been looking at SVN and Bzr. How do they stack up? Any experience? What are the differences?


Answers

Add Answer
  1. By Jesse Babson on Oct. 03, 2007

    It depends on what you actually need. Things to ask:
    1) Do you need web-access?
    2) Do you need ssh access?
    3) Do you need IDE integration?

    CVS is the oldest and has been around for the longest - it is built on top of RCS. Subversion uses an RDBMS at the back end.

    So, provide some more info on what your needs are. I've used CVS and SVN and can offer some thoughts.

    2 Votes
  2. By Marty Bennett on Oct. 09, 2007

    Good questions.

    1) Web-access: Yes - desired, but not required.
    2) SSH: Well, not sure I follow. I could use a CLI to access the source code system over SSH? Yes, that would be required too.
    3) I'm looking to rally around Eclipse, but I could use just vi and make files.

    Basically, I need a system that is flexible to allow our team to use tools they are comfortable with, whether Eclipse or vi. They need to be able to check-in/check-out code into a repository that I control.

    HTH.

    1 Votes
  3. By Jesse Babson on Oct. 12, 2007

    Well, eclipse can use both SVN and CVS. I've personally found CVS easy to set up and use for smaller projects. You can access it from the command line, and there is built in eclipse support.

    SVN is newer, and more robust. You can easily get a free eclipse plugin for that too.

    SVN has several plugins to windows explorer, etc. so you can use tortiseSVN or something and not be bound to your IDE, should you wish to use vi (or emacs!) and make files.

    0 Votes
  4. By Roland Pashniev on Aug. 29, 2008

    svn much more easy to setup and have no cost to maintenance(server and clien part),

    many peoples migrate from CVS to SVN

    I think SVN will be good choose


    0 Votes
  5. By Jason Wang on Aug. 29, 2008

    svn of course


    0 Votes
  6. By Allan Cayanan on Aug. 29, 2008

    One thing to note about CVS is that it cannot track those renamed or deleted files, so you might consider SVN as it supports these CVS incapabilities. And, its more robust and supported by many IDEs.


    0 Votes
  7. By Philip Rud on Aug. 29, 2008

    In general there currently are two mainstream types of versioning systems.

    1) "Classic" centralized versioning systems, like CVS, Subversion and so on - when you're developing a closed source project with your team, and your changes are quite straightforward without creating many branches and merging them later, then SVN is just the best thing to look at. In general SVN was kind of a try to make a 'good CVS', so there's no point to look at cvs now - it's just the old thing.

    2) If you want to make your repository more flexible and use kind of really modern things you could take a look at modern *distributed* versioning systems like Mercurial or Git. Both of them are very cool and popular things. If you're looking for a pythonic one (but still fast) take a look at Mercurial - Netbeans and OpenJDK projects are using it as their vcs. From other side git written on C, and is used as a vcs for the Linux kernel (nothing to add:)


    0 Votes
  8. By sugiarto udah on Aug. 29, 2008

    at my experience, CVS required user as system user, so user which want to use CVS, have to registered as user in system. But with SVN, it is not required


    0 Votes
  9. By Jason Mei on Aug. 30, 2008

    subversion is used in my company.


    0 Votes
  10. By china long on Aug. 30, 2008

    svn


    0 Votes
  11. By Peter Kremer on Jan. 23, 2009

    Here is an article comparing them: http://bazaar-vcs.org/BzrVsSvn

    Our vote in the company was 4-3 in favor of subversion over Bazaar. I prefer Bazaar, as did the other two most experienced developers. So much for democracy. The article has some good information about the pros and cons of each.


    0 Votes
  12. By Nikos k on Jan. 25, 2009

    Subversion seems to be the better solution since it is easier to learn and use and it's supported by every tool I've come across so far. It's even supported by the web host I use (dreamhost offers subversion hosting through their control panel) but you can easily setup your own.


    Unless you have some special needs that can't be addressed by svn then I can't recommend anything better.


    0 Votes
  13. By zeshan mushtaq on Jan. 26, 2009

    subversion is best it provides you good facility over the internet and also code merging is good. no resource deadlook etc. easy to install and configure lot of plugins and clients for all platform are availables


    0 Votes
Share your knowledge