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. The choice is clear by BoBaBrain · · Score: 5, Funny

    Shouldn't we just use whatever source control system the CVS developers use?

    --
    I am a Karma Library.
  2. Re:Simple answer. by SN74S181 · · Score: 4, Funny

    Now it's just a matter of some GNU programmers coming out with a knock-off version that's not as good, but good enough. First, though, we need to come up with a name. It has to be a clever twist on BitKeeper.

    I nominate:

    'ByteLoser'

    Who wants to slap up the SourceFarce page and start working on the icon?

  3. Re:Version control system minimum requirements by Mika_Lindman · · Score: 5, Funny

    13. allows version numbers larger than 1. I'm tired of all open source being with version numbers like 0.997