From SVN to Mercurial: Part 1

Recently, we have begun dividing our work amongst several teams on different branches. This prompted us to start moving from Subversion (SVN) to Mercurial.

We have actually had great success with Subversion (SVN). We moved from CVS several years ago and have never regretted it. With it's improved rename and move support and cleaner branching SVN was an easy decision.

Now we find ourselves, once again, pinning for the capabilities of a Version Control System that we don't have. We are also in the throws of moving build servers from Luntbuild to Hudson. So, over the next few posts I'll discuss our experiences with moving from SVN to Mercurial.

Comments

Anonymous said…
good choice ;)
Unknown said…
Thanks! So far we're very happy with it...lots of back and forth about GIT versus Mercurial.
I try to identify the major issues to achieve the real-life success.
Unknown said…
It's a good piece of work. I have no words to express my gratitude. Hopefully waiting for your next post. Essay writing services
Browsing the latest news from the trendiest accounts and hashtags of other Instagram users, downloading photos in a wink with pictame
Anonymous said…
Just in time! This resource is what I am needing right now. Thank you for sharing. check this site
Luna Morris said…
Interesting read on the move from SVN to Mercurial. The comparison makes the benefits, challenges, and workflow changes of switching version control systems easy to understand. certified wealth manager

Popular posts from this blog

New Pattern: CPT (Can't Polish a Turd)

Getting the Data out of my Controller Tests

Microsoft MVC or Is the Monorail off it's track?