On Feb 11, 2:58 am, Henrique de Miranda Gontijo <[email protected]> wrote: > Hi guys, > > I need yours advices about a great SCM tool to manage a project where we > work withs evolution and supporting. Because of the business rules there are > times we get working with 3 or 4 branches. The team is small - 3 guys. > We are considering leaving CMVC (yes, it's the old IBM tool) instead of a > new, (maybe) free, robust and friendly SCM tool. The great fear today is how > we can have all branches well integrated because the responsability to > update all branches will be in the hand of the developer. > I'd appreciate if you share yours experiences and suggestions regarding it.
SVN is the safe choice and improved branching in 1.6 a while ago (http://svnbook.red-bean.com/nightly/en/svn- book.html#svn.branchmerge). Git/Mercurial is more risky since general tool support is less mature. I found this article to be a great introduction in how Git differs from CVS/SVN: http://alblue.blogspot.com/2010/02/git-for-eclipse-users.html (despite the title, Eclipse only comes into play in the very last paragraph - and yes, Eclipse and Netbeans couldn't agree once more, with Eclipse going with git and Netbeans with Mercurial). -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
