Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm
To: <gump@jakarta.apache.org>, <mockobjects-java-dev@lists.sourceforge.net>
Subject: Re: [MO-java-dev] compilation problem for mockobjects
References: <015a01c3ea97$88bdb080$6a4041db@vma>
	<m3ptcvnrlg.fsf@bodewig.bost.de>
	<000401c3eb03$557f2110$9865fea9@backpack>
From: Stefan Bodewig <bodewig@apache.org>
Date: Wed, 04 Feb 2004 14:05:59 +0100
In-Reply-To: <000401c3eb03$557f2110$9865fea9@backpack> (Nat Pryce's message
 of "Wed, 4 Feb 2004 09:43:21 -0000")
Message-ID: <m3fzdrhu4o.fsf@bodewig.bost.de>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Wed, 4 Feb 2004, Nat Pryce <nat.pryce@b13media.com> wrote:

> Considering what Gump is meant to be used for, would it be better
> for it to be "edge triggered" rather than "level triggered".

It depends on the community you want to reach.  Sometimes it takes
repeated nagging to get the message through.  Sometimes you generate
the opposite effect by nagging, i.e. mails get ignored.

> That is, should it send a message when a project fails to build, and
> then sends a message when the project builds successfully again,
> instead of sending a message every time it fails to build a broken
> project?

Yes, this would certainly be an option, and I think much of the
statistics sthe new Python implementation of Gump collects can be used
for that.  We also generate RSS feeds that contain exactly these types
of status changes IIRC.

The email based nagging system has been Gump's traditional approach
and it has done an outstanding job in many cases.  I agree that it is
plain annoying if it comes unwanted.

Maybe we can improve the nagging part in the Python implementation to
be configurable on a project level.  Some projects may want a nightly
report even on successful builds as confirmation, others may only want
to get notified on status changes (as you describe it).

Stefan