Mike Mackrory wrote: > I was hoping I could tap into some of the experience of the group. I've > been tasked with researching options for a new Source Code Control System. > Our current system doesn't allow us to check in/out code or roll changes > back, hence the need to find a new one. > > Does anyone have any recommendations for systems they would recommend that I > look at, or avoid? The primary development machines run on Windows and it > would be preferable that the code itself be stored on a Linux box.
Here are a couple more for your list. Git Git is the vcs that is used (most famously) for the Linux kernel. http://git.or.cz/ Here is an audio interview with the maintainer of Git http://twit.tv/floss19 Interesting thing about Git: everything is cryptographically verifiable. Bazaar Bazaar is most famously used by Ubuntu http://bazaar-vcs.org/ I am using Bazaar for one of my projects (one man, one project) mainly for maintaining a history of what I am doing. It has been useful in the cases where I hosed something and needed to roll back or look at old code. It works well for that, but I'm sure it can handle much more. (hence Ubuntu using it for everything) Both of those systems are designed to handle Distributed versioning as well as a central versioning. This means developers working on their workstations can maintain their own versions of code between checkouts. This is handy for running through multiple ideas of how to do something, then taking the one that works best and checking it in. I think you can use tools designed for Subversion with Git, but I don't know if Bazaar has a Subversion interface. I'm going off of memory for that, so you might want to double check if that is a requirement. Orson _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
