Yesterday, the Subversion project announced that they were moving development of Subversion itself to Git. It was, unsurprisingly, an April Fool’s prank, but the level of detail in the ticket’s comments was pretty convincing—I definitely fell for it.
But really, the joke’s on them, since it’s so eminently plausible to want to switch to Git from Subversion. Nobody uses Subversion because they want to: they’re prisoners of legacy systems. And anyone who actually claims to love Subversion must have Stockholm Syndrome.
I see this at Automattic, where we use Subversion. There’s a lot of agitation for a move to Git, but Etsy’s Git migration shows that this can be a huge project. Still, I’m seeing a lot of people internally move outside of the standard Subversion workflow, embracing either a “work in Git, deploy to SVN” workflow, or even fully embracing GitHub as the primary development platform, like Jetpack.1
Although some people find Git confusing at first, that’s usually because they’re looking at it through Subversion-tinted glasses. We have one internal project using GitHub that many of our designers are collaborating on, and they got up and running with a branch and merge workflow almost painlessly. It’s been fantastic for collaboration on a fast-moving project that would have been basically impossible if we hadn’t been using Git.
- Although they still have to sync back and forth with WordPress.com’s SVN setup. ↩