Re: [Openoss-devel] Eclipse encouraging migration ot Git

[Craig G. (opennms) <cg...@op...>]

Hi Marc,

Thanks for this. Very timely. I was obviously working on earlier 
information.

I have no problem in principle moving from subversion to GIT. OpenNMS 
moved from subversion to GIT on sourceforge about 2 years ago and the 
developers are very pleased with the flexibility it gives. However I 
think there are a few lessons we found which are worth looking at

1.  I think changeing from SVN to Git is a different decision to moving 
from Sourceforge to github since both sourceforge and github will 
support git. OpenNMS looked at making the move to another hosting site 
but a couple of things were important thet kept us on sourceforge
a) We wanted to maintain the history of the project and didnt want to 
export the entire subversion history into git. Having both the 
subversion and GIT version in one place made more sense.
b) We wanted to maintain the google searchers and mail lists history 
since it showed the projects longevity and many goggle searches etc. 
sent people to the well known site.
c) we host our own documentation wiki and Jira bug tracker so didn't 
really need the sourceforge or github tools.

2. making the transition to Git
It took some time to get the OpenNMS team familiar with the Git way of 
working which is different to what is done in subversion. There is a 
learning curve (which I haven't completed myself). We needed developer 
documentation and also a clear release strategy to be worked out before 
we made the switch.  In practice we maintained duplicate copies for one 
release in both version systems until we were ready to make the jump. 
This recognised that we had to migrate an number of developer and 
feature branches and a merged release during the transition.

3. working on windows
OpenNMS developer uses git on *nix developer environments
There are certain peculiarities to working in windows.
There is a tortoiseGit tool but there are some reported problems working 
with it and I haven't used it. http://code.google.com/p/tortoisegit/
Natively I use a tool called GitBash which provides a command line 
environment on windows for checking out git repos http://msysgit.github.com/
There is a git tool for eclipse egit http://www.eclipse.org/egit/ which 
would need to be installed in the work bench installer to allow eclipse 
checkouts from git.

In short, we would need someone to test Git working on windows, work out 
our the branch and release strategy and provide training and 
documentation for everyone.  Ideally we would need a release manager who 
is familiar with Git to nurse us along. Getting ready for any transition 
would need to be worked on in parallel with  the ongoing development 
work in order to avoid a hiatus where everything stops.

Finally, and importantly, I think we really don't want to end up with 
one code version system inside the TM forum and a different one outside. 
So what is the plan to migrate TIP inside the TM forum also to Git? In 
the scheme of things, I personally believe there are more pressing 
issues to put time into than swapping what is at present an adequate 
code management system. Remember, in your post, Tigerstripe were moving 
to Git from CVS which is a much older and less flexible solution that 
Subversion. I could see strong arguments for jumping from CVS to Git but 
the need to jump from Subversion is to my mind less pressing.

Such are my thoughts

Craig












On 12/10/2012 08:06, Flauw, Marc wrote:
>
> Dear all,
>
> You may have seen the mail from Duncan that I re-forwarded indicating 
> that Tigerstripe will be moving to Git on Oct 15^th .
>
> This mail was pointing to an Eclipse page: 
> http://www.eclipse.org/projects/scmcountdown.php 
> <http://www.eclipse.org/projects/scmcountdown.php>  indicating that 
> "Eclipse projects are encouraged to start planning their migration to 
> Git."
>
> It has also some interesting stats: 64.7% of Eclipse projects use Git 
> as repository, only 14.9% are using SVN. The rest is using CVS and 
> this support will go away on Dec 21, so those projects will move to Git.
>
> This is bringing a new light on this discussion and is showing the 
> need to have a good idea of what would mean a migration of JOSIF to 
> Git: tasks and cost.
>
> Any volunteer to start this?
>
> Best regards
>
> Marc
>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
>
>
> _______________________________________________
> Openoss-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openoss-devel