db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: 10.3 bug fixing candidates
Date Fri, 13 Apr 2007 22:37:18 GMT
On 4/13/07, Knut Anders Hatlen <Knut.Hatlen@sun.com> wrote:
> Kathey Marsden <kmarsdenderby@sbcglobal.net> writes:
> > I was looking through the open issues for good 10.3 bug fixing
> > candidates and came up with this list for starters.  If no one objects
> > we can go with the same procedure as for 10.2 where we mark high value
> > fix candidates  as Fixin the current release. I'll mark these Fixin
> > 10.3 and update the HighValueFixCandidates page unless anyone objects.
> There was some discussion about the use of Fix-in a couple of months
> ago, and I think we agreed that the Fix-in field should only be used to
> indicate which versions the assignee expected the issue to be addressed
> in. That is, Fix-in should not be set for unassigned issues.

Instead of setting the Fix-in, how about using the Urgency field to
reflect that the bug is a high-value fix?


View raw message