We have two issues with Subversion: - it requires a certain discipline: we need branching in our workflow and this is handled mostly by convention in a subver

We have two issues with Subversion: - it requires a certain discipline: we need branching in our workflow and this is handled mostly by convention in a subversion repository. We have "branches" that were created by less careful colleagues by copying subdirectories of trunk to the branches folder. - all the tooling developers fled to work on making git bearable. It seems that there is good money in sugarcoating got and none in making good tools for Subversion (awareness of branches in Jenkins, decent code review...). We have a budget, but that does not compensate for the lead that git has in that regard. Other than that, subversion fits our needs. It just works.