On 10 April 2010 03:25, pepe <p...@betterrpg.com> wrote: > Also take into consideration that we have never used a version control > system so my questions might just be due to lack of knowledge and/or > understanding as of how to use the VCS.
Well, distributed version control is going to be your friend here, but you are going from a standing start to pretty much the most complicated use of it. Personally, I'm a Mercurial fan, but Git is very similar. Either way, both tools allow developers to maintain their own clones of a central repository, and to make as many commits as they like to give them a safety net as they work. At whatever interval (normally for me, it's when a "feature" is working and passing tests) their local changes are pushed up to the repository (and merged if necessary, but if they've been doing lots of little commits, the merge is often done for you). At that point, cloning out features to the other branches would need to be done (probably by a dedicated person who knows the individual systems well). "propagate those changes selectively" is almost certainly going to mean a large level of manual intervention, but again, this is much easier to decipher with the incremental commits that become the signature of DVCS. Check out www.hginit.com for a very good "getting started" guide for Mercurial. I use a "Turnkey Linux" server for my Mercurial machine, but you can install it on anything and configure yourself. The benefit of the Turnkey machine is that you get up and running in about 15mins, and can play with a few different systems for comparison. http://www.turnkeylinux.org/revision-control -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
