[jbosstools-dev] Git - worth it or not ?

[Brian Fitzpatrick]

Yahor, I agree with #2 for sure. 

However I suspect that the tooling for #1 will stabilize and improve over the next few months to a year as the Eclipse teams who are working on the jGit and eGit projects stabilize the tooling and make it better. 

--Fitz

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Yahor Radtsevich" <yradtsevich at exadel.com>
To: "Max Rydahl Andersen" <max.andersen at redhat.com>
Cc: "Brian Fitzpatrick" <bfitzpat at redhat.com>, "jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Monday, February 14, 2011 11:39:02 AM
Subject: Re: [jbosstools-dev] Git - worth it or not ?


My main contras for Git: 


    1. It is poorly integrated with Windows and Eclipse. 
    2. Git repo will be too big. Thus this is a question for me will be commits faster or not. It will big because: 


        1. JBoss Tools SVN consists of pretty coupled projects, so we have(?) to create a single Git repo for all of them. 
        2. There are a lot of binaries (jars, images, videos, giant zip-files, ...). If we want to have all SVN history in Git, we have to add all these binaries to the mirror. I expect it will take approx 5GB (SVN repo itself takes 7GB now). 

Anyway, Max, if you succeed with creation of the mirror, please share it. I would like to play with it too :) I tried to create a Git mirror some time ago, but after a lot of attempts I decided that it is not possible on Windows without direct access to the SVN repo. 


-- 
Yahor Radtsevich 

On Mon, Feb 14, 2011 at 7:14 PM, Brian Fitzpatrick < bfitzpat at redhat.com > wrote: 


Hey Max... 

I think there will definitely be some challenges as far as migrating SVN to Git, but the long term benefits might outweigh any short-term pain. As we chatted about on IRC, the issues will include things like... Do we end up with one large Git repo to mimic what we have with SVN? (Not ideal) Or do we split up all the modules into their own Git repos, which explodes our code into a million projects, some of which won't be touched often if at all? 

That said, I think it will be an interesting experiment to see how complicated maintenance gets with the git mirror. 

I certainly want to see if it's better or worse before we make the commitment. :) 

--Fitz 
_______________________________ 
Brian Fitzpatrick (aka "Fitz") 
Senior Software Engineer, SOA-P 
JBoss by Red Hat 




----- Original Message ----- 
From: "Max Rydahl Andersen" < max.andersen at redhat.com > 
To: "jbosstools-dev" < jbosstools-dev at lists.jboss.org > 
Sent: Monday, February 14, 2011 8:32:34 AM 
Subject: [jbosstools-dev] Git - worth it or not ? 

Hi, 

I must say i'm pretty impressed with Git and how easy or rather *fast* to use compared to svn. 

I'm still not convinced on how/if we should move jboss tools repo to a git repo or rather a set of git repo's 
to make things more modular and easier (in some respects) to maintain compared to a full svn tree. 

Thus i'm currently trying to setup a git mirror of our svn repo - to at least use as a testbed for git. 

Thoughts ? 

p.s. this is no way a commitment that we'll move to git - just a start now that GA is about to go out the door 
to see if there are things we can do better to make life easier for us ;) 

/max 
_______________________________________________ 
jbosstools-dev mailing list 
jbosstools-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/jbosstools-dev 
_______________________________________________ 
jbosstools-dev mailing list 
jbosstools-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/jbosstools-dev