Co-Existence Subversion & Git

You are definitely not alone when you have a wide range of Subversion repositories, but want to move to Git.
Or you have a lot of users who want to use SVN, but also a lot of users wanna use Git instead.

Introduction

There are even more reasons to have more than one VCS:

• Migration, Git is more sophisticated than Svn and more reliable (more than one point of restore against one point of disaster).
• Co-existence, preparing the migration mau need both systems to work next to each other.
• Proof of Concept, before deciding to migrate you want to know if the solution works for you.
• Mixed, one or more of the above mentioned items.

Git is powerful, but has also a steep learning curve, making the implementation difficult.

The first very basic question is can you have 2 VCS systems next to each other?
The common answer is Yes, the more advanced answer is Maybe, and the smart answer is ...

Git vs SVN adaption

Of coarse the normally answer should be stick to just one VCS, but that is beyond the main question, in the end you want to have only one VCS, but:

• Many scripts are working with SVN
• Migration of all scripts may not be possible or not wanted at the moment.
• The Subversion-workflow is easy, embedded and well understood
• The adaption of Git is difficult due to the its steep learning curve.