Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: "Noel J. Bergman" <noel@devtech.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: RE: [PROPOSAL] End Gump builds for sandbox projects
Date: Mon, 1 Mar 2004 22:55:03 -0500
Message-ID: <NBBBJGEAGJAKLIDBKJOPGEEJHLAB.noel@devtech.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <00a001c3ffeb$827af700$49018551@oemcomputer>
Importance: Normal

> This is a proposal to begin to end the abuse of the sandbox.

I agree with your concern, I disagee with your method.

We are awaiting new hardware.  One of the new machines will be dedicated to
GUMP processing (possibly some other related tasks).  My understanding, and
there are reasons for this, is that the output from the machine will be
reports.  The builds will not be available at all.  That addresses your
concern without breaking the value of GUMP.

  -1 to kill GUMP for sandbox
  -1 to kill it for unreleased projects

Remember: GUMP is for *our* use, and the latter point would mean that no
project within the ASF could even start to use a library until after it had
a formal release, which could lead to a Catch-22.  The whole purpose for
GUMP is to catch problems EARLY in the development cycle, not to be a build
and test server for released components.  The new GUMP configuration will
eliminate the problem of people using GUMP builds, so let's not throw out
the baby with the bathwater.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org