Message from discussion
git, future directions
Received: by 10.115.22.9 with SMTP id z9mr332050wai.28.1235687262717;
Thu, 26 Feb 2009 14:27:42 -0800 (PST)
Return-Path: <lda...@gmail.com>
Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187])
by mx.google.com with ESMTP id k19si12616552waf.0.2009.02.26.14.27.41;
Thu, 26 Feb 2009 14:27:42 -0800 (PST)
Received-SPF: neutral (google.com: 211.29.132.187 is neither permitted nor denied by domain of lda...@gmail.com) client-ip=211.29.132.187;
Authentication-Results: mx.google.com; spf=neutral (google.com: 211.29.132.187 is neither permitted nor denied by domain of lda...@gmail.com) smtp.mail=lda...@gmail.com
Received: from [10.0.1.6] (c210-49-138-194.kelvn1.qld.optusnet.com.au [210.49.138.194])
by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n1QMRdqg011014
for <esoe-dev@googlegroups.com>; Fri, 27 Feb 2009 09:27:40 +1100
Message-Id: <BE7C2473-6DC7-4EB3-B9B4-EAC63FEF8A87@gmail.com>
From: Luke Daley <lda...@gmail.com>
To: esoe-dev@googlegroups.com
In-Reply-To: <EF21CAFB-258E-4DFB-8986-85981E155D03@intient.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: [esoe-dev] git, future directions
Date: Fri, 27 Feb 2009 08:27:38 +1000
References: <EF21CAFB-258E-4DFB-8986-85981E155D03@intient.com>
X-Mailer: Apple Mail (2.930.3)
On 26/02/2009, at 6:22 PM, Bradley Beddoes wrote:
> I'd like to get others input on moving ESOE code bases to GIT backed
No argument from me. The only thing I would be concerned about is =20
making sure that the tooling supports it. The project needs continuous =20=
integration and a repository inspector, and ideally an issue tracker =20
linked into both of these. I have used the Atlassian tool set to do =20
this in the past which works well, but I don't think they are =20
supporting git yet=85 yep just checked and they still aren't though they =
=20
plan to.
It makes sense to me to move this project to Codehaus or even Apache. =20=
Although Apache is quite strict on the projects they host so Codehaus =20=
might be a better choice. They have all the tools and admin interfaces =20=
to manage them, not to mention free bandwidth. It also adds a certain =20=
aspect of credibility to the project by having it hosted by a well =20
known hoster of open source projects. Plus, it allows the developers =20
to focus on developing rather than installing and configuring software.
I am not a hardcore git user so I may not have seen the light yet, but =20=
I would rather stick with svn because of the support for it from =20
FishEye and Bamboo for the time being. Individual developers can =20
always use git+svn locally to get _some_ of the features.=
|
