Yes, too bad.
I've been thinking a bit more about your git-branch approach, I use the "GitHub for Mac" app quite a bit, which makes it very easy to pull code from that site, but also to switch branches, check in changes, and even submit pull requests. There's also a "GitHub for Windows" app. On Linux, I assume everyone will be familiar with the command line, so no issues there.https://desktop.github.com
Maybe there's a not-too-complex-or-brittle way to describe the setup process for newcomers. The advantage being that this mechanism exists today, once you know how to switch branches. Something like: download/install the IDE, download/install GitHub, checkout a repo in the right place, restart the IDE.
I don't know how easy it is to maintain an entire set of branches. What if you want to apply a change which needs to carry through in multiple, or even all, the branches? Use two separate repositories next to each other, perhaps? One single-branch with common stuff, and one multi-branch with references to the common stuff?