On Fri, Aug 28, 2009 at 5:15 PM, Bryan Tong Minhbryan.tongminh@gmail.com wrote:
We could take a look at Bazaar. It has pretty good SVN integration.You can create a (centralized) checkout of an SVN repo and when you commit into that centralized checkout from your local Bazaar branch it should commit into the master SVN as well (as I understand it). This would allow peaceful concurrent use of a centralized and decentralized version control system (although Bazaar itself supports centralized use as well).
git-svn works fine for this. I've been using it for ages. Chromium is one project that primarily uses SVN, but semi-officially uses git, with a repository you can clone and commit to and have everything work.
Plus it works natively on Windows without icky POSIX emulation layers.
POSIX emulation layers aren't a problem, it's the user experience that matters in the end. On Windows, I've used SVN extensively, Mercurial a few times, and git even less. My impression is that git is still not nearly as nice on Windows as Mercurial or Subversion -- I don't think it has the fancy context-menu integration and so on. (Does it? I haven't checked lately, so I might be outdated.) If we switched to git, we might annoy some TortoiseSVN users by forcing them to switch to less convenient software.
It would be interesting to consider keeping SVN as the primary repo for now, but with officially-maintained git checkout for those who want it. If Windows support for git improves, we could consider retiring the SVN repo eventually.