migration from svn to something else.

[Thomas Velthoven]

two questions:

1 We use -ondemand. You guys are asking to change our SVN to some other service. We are interested in moving to git or mercurial. How will this happen?

2 We like a specific feature of svn and jira and wonder if this is available in mercurial or git. Svn does not let us commit without a valid jira id in the comment. We'd like to keep that. Is is possible? How?

[Stefan Saasen · Accepted solution]

Hi Thomas,

Regarding your first question: Our migration guide on http://go-dvcs.atlassian.com/display/aod/Migration+Introduction tries to help you answer your first question.

As an example, the page on http://go-dvcs.atlassian.com/display/aod/Migrating+from+Subversion+to+Git+on+Bitbucket outlines the migration process from Subversion to git.

Regarding your second question. This depends on your concrete migration plan (i.e. do you move to Bitbucket, a behind the firewal hosting solution like Stash or something else) but it in general this is less useful with DVCS compared to SVN. With local commits the validation that would happen on a push could mean that you'd have to rewrite a number of commits (potentially commits that are result of a merge). Ideally the verification of the commit message happens on commit which in DVCS means on the client. For git you could use the `commit-msg` hook (http://www.kernel.org/pub/software/scm/git/docs/githooks.html).

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format (if the project has one). It can also be used to refuse the commit after inspecting the message file.

Hope this helps.

Cheers,

Stefan