On Wed, Apr 13, 2011 at 9:55 AM, Rob <[email protected]> wrote: > I am looking to implement a version control system with a new client, > and wanted to see what others were happy with.
Subversion is more or less the standard these days. It's been around for a long time, the tools are very mature, and there's tons of documentation and help resources available. Git is the up and comer in the distributed version control world. Many people swear by it, and even use it in conjunction with SVN, but it's still new-ish and other than command line tools (which are fine by me!) the tools are still immature compared to what's available for SVN, particularly where an Eclipse plugin is concerned. They're getting there but they're not up to the level of the SVN tools yet. I know precious little about Git so take what I'm saying for what it's worth. I personally haven't had enough issues with SVN to be prompted to switch to Git, but the distributed/offline nature of Git does appeal to me so I see myself making the switch at some point. If you're looking for tried and true, use SVN. If you need some of the specific features Git offers, I've heard from many people whose opinions I trust that it's great. Just be prepared for more rough around the edges tooling for a while. As for builds, unless you're on a hosted service that offers that as a feature you typically wind up writing build scripts using something like ANT and run with a cron job, or you can use something like Cruise Control or Jenkins (formerly Hudson) to handle some of this for you. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
