I migrated those two repositories today :
https://github.com/gatein/gatein-dep
https://github.com/gatein/gatein-parent
they are not an SVN migration but rather I recreated all the tags and branch from the SVN
as the migration was failing and what really matters are the release (and not the
changes).
who is volunteering for a quick review ?
Julien
On Apr 17, 2012, at 3:57 PM, Boleslaw Dawidowicz wrote:
Hi,
I would like to give you some status about migration from svn to git and ask for your
help in the process.
1) I just switched off svn write access to anything besides EPP bits. Let me know if you
have any urgent commits to make
2) Today we migrated most of svn repositories to github - as previews.
https://github.com/mstruk/gatein-wci-STAGING
https://github.com/bdaw/gatein-wsrp-preview
https://github.com/bdaw/gatein-mop-preview
https://github.com/bdaw/gatein-sso-preview
https://github.com/bdaw/gatein-simplecaptcha-preview
https://github.com/bdaw/gatein-common-preview
https://github.com/bdaw/gatein-packager-preview
https://github.com/bdaw/gatein-dep-preview
https://github.com/bdaw/gatein-parent-preview
Once it is verified that those were migrated properly we will promote them (meaning
renaming and donating to "gatein" organization on github). This can happen this
week - depends on how fast we are able to verify all the bits.
3) We need help with verification process. Any extra eyes are welcome.
Here are some notes about what should be checked for each repository
I) If "git branch -a" matches list of branches in svn
II) If "git tag -l" matches list of tags in svn. It can be both not all or too
much entries in git - sometimes some "junk" pass thru.
III) If master builds…
IV) If pom.xml contains proper "<scm>" definition pointing to github and
proper release plugin properties. Here is the example:
<scm>
<
connection>scm:git:git://github.com/gatein/gatein-pc.git</connectio...
<developerConnection>scm:git:ssh://git@github.com/gatein/gatein-pc.git</developerConnection>
<
url>https://github.com/gatein/gatein-pc</url>
</scm>
<properties>
…
<!-- maven-release-plugin -->
<useReleaseProfile>false</useReleaseProfile>
<arguments>-Prelease</arguments>
<version.release.plugin>2.2.1</version.release.plugin>
<pushChanges>false</pushChanges>
<autoVersionSubmodules>true</autoVersionSubmodules>
<!-- buildnumber-maven-plugin : needs 1.0 for git -->
<version.buildnumber.plugin>1.0</version.buildnumber.plugin>
</properties>
I updated only pom.xml in master with those. Not in branches.
V) Check out whole svn structure of the component and compare random tags and branches
between svn and git.
Example:
git checkout 2.1.0-CR02
diff -qr . /some/path/svn/gatein/components/pc/tags/2.1.0-CR02 | grep -v -e
'DS_Store' -e 'Thumbs' -e '.git*' -e '.svn'
Bolek
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev