ESOE Project on git? - ESOE Development

Message from discussion ESOE Project on git?

Bradley Beddoes

More options Jun 18, 10:41 am

From: Bradley Beddoes <bedd...@intient.com>

Date: Thu, 18 Jun 2009 10:41:24 +1000

Local: Thurs, Jun 18 2009 10:41 am

Subject: Re: [esoe-dev] ESOE Project on git?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

Hi Shaun,

My experience with other large projects and Git has been the single
repository approach with top level directories for each sub component.
I've used a couple that have gone the other way. Overall there are
positives and negatives to both.

What I find does really get painful with the single repository
approach is folks storing binaries (jars etc) that cause pulls to take
a long time especially from international sources. ESOE to date has
done a very good job of not storing any binary in SCM and has made
good use of Ivy et al for dependency resolution.

GitHub is a lot more useful as a web-app with single repository in my
experience.

I guess as long as the dependency resolution approach continues and is
strongly enforced I'd be leaning towards a single approach but it
doesn't concern me either way.

regards,
Bradley

Bradley Beddoes
Intient Pty Ltd

http://www.intient.com
Twitter - http://twitter.com/bradleybeddoes
Facebook - http://facebook.com/bradleybeddoes

On 17/06/2009, at 9:23 PM, Shaun Mangelsdorf wrote:

> Hi All,

> It's come time again to revisit the idea of using git for
> development of the ESOE project. A few things have changed since
> this was last discussed, not the least of which is the transition to
> Redmine (http://www.redmine.org) for managing the project.

> With the revamped project site, we can now use (almost) any VCS we
> want. The only feature missing is continuous integration which we
> can address later, outside the scope of this discussion.

> I'd be keen to hear any arguments against git, but in the absence of
> any strong opposition I would say the move to git is inevitable. I
> believe that tool support is now solid enough that we can make the
> transition smoothly. There is one main question I put out to the
> esoe-dev list:

> How should the Git repository be structured? I see two options really:

> - One monolithic git repository with a mirror of the current
> structure of the svn trunk

> Advantages:
> * Atomic branching and tagging, treating all the code as a unit.
> * Only one history timeline to manage.
> * Repository introspection will continue to function properly -
> Redmine can only properly link one source repository with a project.

> - One git repository per project (broken down per Eclipse project)

> Advantages:
> * More "correct"
> * Easier for other projects to consume our code as submodules

> I'm keen to hear of any more advantages to either approach, or any
> other thoughts. My preference currently is for one repository, but
> it's certainly not set in stone.

> Regards,
> Shaun Mangelsdorf

Reply to author Forward