Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44234148.8040902@sbcglobal.net>
Date: Thu, 23 Mar 2006 16:46:00 -0800
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: IRC chat summary
References: <17443.14675.357553.540531@gargle.gargle.HOWL>
 <44233AA7.4030109@sun.com>
In-Reply-To: <44233AA7.4030109@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David W. Van Couvering wrote:

> One comment: I do hope that once we hit feature freeze that we can
> spend some time stabilizing the release, having a "bug-fix fest".  We
> don't *have* to immediately go to GA release as soon as feature freeze
> is complete.  Maybe we could in the past, when we had fewer bugs and
> fewer contributions, but now perhaps we need a longer stabilization
> period. Maybe a release criteria could include a reduction in bugs by
> a certain percentage.
>

In addition to release criteria, it might be prudent to have some sort
of  periodic comprehensive quality checkpoint and have some some sort of
criteria for continuing to accept new features.  Folks get so head down
on their tasks, but sometimes the big picture needs looking at.  I think
at least a "Regression" checkbox in  Jira could  flag regressions and we
could set some sort of minimum acceptability standard for that. 

Kathey