db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Fix Version for 10.2 unassigned issues (was Re: remaining 10.2 blocker)
Date Tue, 25 Jul 2006 17:37:01 GMT
Kathey Marsden  wrote:

>>    * Mark Fix Version 10.2 for unassigned issues if we  think it is  
>> a high value fix that  could be fixed in time for the release.
>>    * Iteratively adjust Fix Version as we get closer to the release.
>>    * Use Blocker/Critical to mark  must fix issues.
>> Details here:
>> http://www.nabble.com/prioritized-10.2-bug-list-tf1932945.html#a5301968
Rick Hillegas wrote:

> Yes, please. This is an easy policy for me to wrap my mind around.
I think this use of the fix version  field is a good start towards a 
framework for community bug review.    I do have some trepidation about 
overloading priority this but don't have  a better alternative.

 It would be great if everyone could please check the unassigned 10.2 
issues and change Fix Version if needed.  Are there any that are not 
high value fixes or cannot  reasonably be resolved by 10.2 (August 10 
for features/improvements, Sept 14 for bugs/test issues?)

The unassigned 10.2  issues you filed:

The unassigned 10.2 issues   for components where you have expertise:
(Qualify the query with the components of interest to you.)

Also folks can  start moving HighValueFixCandidates  into 10.2 but it 
would be good to have the cleanup done sooner rather than later, so the 
really high value bugs stick out to developers looking for bugs to 
pickup for 10.2.


View raw message