Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 96455 invoked from network); 20 Jun 2004 19:13:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Jun 2004 19:13:19 -0000 Received: (qmail 34465 invoked by uid 500); 20 Jun 2004 19:13:20 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 34369 invoked by uid 500); 20 Jun 2004 19:13:19 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 34356 invoked by uid 99); 20 Jun 2004 19:13:19 -0000 Received: from [217.42.133.41] (HELO coderage.org) (217.42.133.41) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sun, 20 Jun 2004 12:13:18 -0700 Received: from CodeRage.ORG (localhost [IPv6:::1]) by coderage.org (8.12.9+Sun/8.12.9) with ESMTP id i5KJCthK004893 for ; Sun, 20 Jun 2004 20:13:11 +0100 (WEST) Message-ID: <40D5E1B7.5020803@CodeRage.ORG> Date: Sun, 20 Jun 2004 20:12:55 +0100 From: Michael Davey User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040116 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gump code and data Subject: Re: [VOTE] retire java gump References: <40C5DA63.1050801@jicarilla.org> <40C5E454.3030503@CodeRage.ORG> <01a801c44e79$2d53c310$3e92b050@ST999999> <07c101c44e7a$fbb00510$e21ce641@sybase.com> <038301c4553b$162177a0$e171eb43@sybase.com> <011f01c45647$5bef4250$3e92b050@ST999999> <71407B98-C298-11D8-8BD7-003065DC754C@apache.org> <000d01c456ae$c75437a0$3e92b050@ST999999> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N robert burrell donkin wrote: > > they could easily be hosted offshore with traditional gump but unless > some people step up and make the offshore builds happen, they won't. > for me, this is the major obstacle and is independent of the decision > to officially stop development of traditional gump. I believe that individual administrators should be able to choose whether to allow downloading of the results from a gump build on a case-by-case basis and therefore that Python Gump should provide a mechanism to enable this. However, I strongly believe that Gump should remain a continuous integration tool and not try to become many things to many people. How about if Python Gump had an option (in a configuration file: on|off) to give the results of the build to a repository tool such as Apache Depot). This means that Depot gets to do all the hard work, all we have to do is work with the Depot guys to define the interface. Hmm, I think i've seen some of the Depot guys hang out here occasionally. ;) -- Michael --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org