Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (herse.apache.org: local policy)
From: Paul Elschot <paul.elschot@xs4all.nl>
To: java-dev@lucene.apache.org
Subject: Re: Tests, Contribs, and Releases
Date: Thu, 17 May 2007 09:51:14 +0200
User-Agent: KMail/1.8.2
References: <Pine.LNX.4.58.0705161448590.24573@hal.rescomp.berkeley.edu>
 <474AF50D-B148-4984-8F41-FBD5DFF06A8E@apache.org>
 <Pine.LNX.4.58.0705170003230.21485@hal.rescomp.berkeley.edu>
In-Reply-To: <Pine.LNX.4.58.0705170003230.21485@hal.rescomp.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705170951.14442.paul.elschot@xs4all.nl>

On Thursday 17 May 2007 09:10, Chris Hostetter wrote:
...
> It could be argued that contribs are not important enough for contrib test
> failures to result in a nightly build failing (I have no strong opinion
> about this).  It could also be argued that while it's good to run test
> against the "core" on a regular basis (ie: in the nightly), test failures
> should not in and of themselves block a release -- so the ReleaseTodo
> doesn't need to include any mention of running tests (I would argue
> against this position very strongly)
> 

I'd rather have a few tests too many, which means that I would prefer
to have the contribs tested by default, and at least before a new release.
Contribs depend on the core, and their tests might also indicate a
problem in the core, even though that is not their intention.

When a contrib fails and is not fixed, that might be a good reason to
remove it from the distribution. With such a policy the present contribs would
also stay up to date, provided their tests are good enough.
Thinking about it a bit more, there is a process to add contribs, but there
is not really a process to remove them. The policy of removing a contrib
before a release when its unit tests fail could make a nice fit for that.

Regards,
Paul Elschot

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