Hi,

I did a dry run migration of two sling bundles:

  https://github.com/rombert/TMP-sling-org.apache.sling.api
  https://github.com/rombert/TMP-sling-org.apache.sling.jcr.repoinit

Please take a look and check if _anything_ is wrong. I think that I
have the process narrowed down more or less using the scripts at [1].

What I know is missing is move tracking. For some reason, the
jcr.repoinit module move is not captured and history starts after the
move from bundles/extensions. ( SVN [2], git [3] ). Any help with what
would be great.

Also I've created a small repo tool setup at 

  https://github.com/rombert/TMP-sling-manifest

The instructions are in the README, but you need to install repo

$ curl https://storage.googleapis.com/git-repo-downloads/repo >
~/bin/repo
$ chmod a+x ~/bin/repo

And then sync your local checkout

$ repo init -u https://github.com/rombert/TMP-sling-manifest.git
$ repo sync

Any feedback is welcome, please do look into the migrated repositories
or maybe propose some tougher migrations. If you are so inclined, the
scripts at tooling/scm/scripts [1] can also use a second pair of eyes
:-)

I'm going to leave this open for a week or so, but maybe after that we
can start migrating from SVN.

Thanks,

Robert


[1]: https://svn.apache.org/repos/asf/sling/trunk/tooling/scm/scripts/
[2]: http://svn.apache.org/viewvc?view=revision&revision=1752162
[3]: https://github.com/apache/sling/commit/087f2d0504dc0b8c38fd298ab9c
29f896321f8c8

Reply via email to