Slashdot Mirror

← Back to Stories (view on slashdot.org)

Designing a New Version Control System?

Posted by Cliff on from the replacing-rcs-and-obsoleting-cvs dept.

tekvov asks: "When Linus Torvalds decided to use BitKeeper as the version control system for Linux there seemed to be a lot of controversy and many challenges to create a better system than CVS. My question is exactly what would this 'better system' look like? How is the subversion project, Tigris, doing at creating a new version control system? Basically, does the Open Source Community need new tools in this aspect of development? And if so, how should these new tools look?"

3 of 536 comments (clear)

  1. Actually by Anonymous Coward · · Score: -1, Flamebait

    Who gives a shit, as long as you get the latest STABLE version. No one gives a shit. Get a life you Linux weenies!

  2. Re:Simple answer. by haizi_23 · · Score: 0, Flamebait

    my. . . you have some CLEVER naming conventions yourself -- SourceFarce -- ho ho ho, good one

  3. Version Control a symptom - not a solution by Anonymous Coward · · Score: -1, Flamebait
    In my opinion, the need for version control is simply a symptom of having exceeded the limit for concurrent development, allowed by the design of the codebase.

    When the programmers need a tool to alert them that they are changing things, that others are changing too, they might catch some bugs, but there will probably be as many that are not caught.

    Two people can never edit the same peice of code, simultaneously with a good result, and when they don't no VC is needed.

    All this version control is simply a poor way of creating the illusion the you can have 100 programmers, finish a 100 man-day program in one day.

    Things take time - great things takes a lot of time.