Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
ESOE Development
+ new post
Home
About this group
Join this group
Message from discussion git, future directions
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Luke Daley  
View profile  
 More options Feb 27, 9:27 am
From: Luke Daley <lda...@gmail.com>
Date: Fri, 27 Feb 2009 08:27:38 +1000
Local: Fri, Feb 27 2009 9:27 am
Subject: Re: [esoe-dev] git, future directions
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author

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  
making sure that the tooling supports it. The project needs continuous  
integration and a repository inspector, and ideally an issue tracker  
linked into both of these. I have used the Atlassian tool set to do  
this in the past which works well, but I don't think they are  
supporting git yet… yep just checked and they still aren't though they  
plan to.

It makes sense to me to move this project to Codehaus or even Apache.  
Although Apache is quite strict on the projects they host so Codehaus  
might be a better choice. They have all the tools and admin interfaces  
to manage them, not to mention free bandwidth. It also adds a certain  
aspect of credibility to the project by having it hosted by a well  
known hoster of open source projects. Plus, it allows the developers  
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  
I would rather stick with svn because of the support for it from  
FishEye and Bamboo for the time being. Individual developers can  
always use git+svn locally to get _some_ of the features.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google