3 ms·
Migrating a large project from svn to another centralized storage is pretty simple but you need support in all your other systems (builds, issue tracking, ...).
by alkonaut 9y ago
Migrating a large project from svn to another centralized storage is pretty simple but you need support in all your other systems (builds, issue tracking, ...). That might limit the choices of centralized vcs available.
Migrating a very large subversion repo to git is not trivial. The KDE team spent a lot of time just developing the tools required to do it
https://github.com/svn-all-fast-export/svn2git https://github.com/svn-all-fast-export/svn2git
But even with those tools it’s still quite a process. If there are lots of large binary assets (often the reason for using centralized to begin with) the adoption of Git-LFS, GVFS etc is a time consuming process.
I have waited years just for the tools to mature (LFS etc) and now I expect to spend a few weeks at least, migrating our single svn repo to git.
Switching from SourceForge should be a no brainer though, completely agree with that - even for projects that stay on SVN.
- jwilk 9y agoWho else offers free Subversion hosting?
- smudgymcscmudge 9y agoGitHub
- deleted 9y ago[deleted]
- jwilk 9y agoAIUI, what GitHub offers is Subversion access to Git repositories; it doesn't host Subversion repositories per se.
- majewsky 9y ago> The KDE team spent a lot of time just developing the tools required to do it KDE was a special case because we wanted to split a monorepo into one repo per application at the same time, yet retain as much history as possible (including across restructurings of the source tree). Also, the massive size of the monorepo (about 1.5 million revisions) made it infeasible to use the standard tooling of git-svn to do it. Most projects will not have these problems. At work, I migrated a rather large application (~500k LOC) from SVN to Git while retaining the entire history, with the standard tooling (`git svn clone && git push`, basically).
- alkonaut 9y agoOurs isn’t even very large, I’d call it “medium”. The svn working copy is around 2GB and the entire 100krev history is about 80Gb. This is easy to handle centralized but we obviously need LFS or GVFS for it to be feasible in Git (keeping all the binary assets AND the 100k rev history is a requirement). Migrating it using git svn is a couple of days (and annoying when it stops half way because of some issue) At least with svn2git we can test-convert including lfs migration in just a couple of hours.
- majewsky 9y agoAh yeah, repos with (a large number of) large binary files are a different story. I'm usually dealing with code only (and maybe some bitmaps for UIs).