On 3/7/11 11:13 AM, Brian Harring wrote:
> Re-read what he stated- it'll convert all existing NEW bugs to 
> CONFIRMED upon migration.  There's a fair number of bugs that are in a 
> NEW state, decent number that have sat for a long while too.  Those 
> bugs aren't 'confirmed'- just like with the new work flow where the 
> dev flips it from UNCONFIRMED to CONFIRMED, leave it to devs to flip 
> the current bugs from UNCONFIRMED to CONFIRMED rather than just 
> marking everything as CONFIRMED.

Maybe I'm misunderstanding something, but it seems we have both
UNCONFIRMED and NEW in the "old" workflow. My understanding is that
CONFIRMED is the new name for NEW, which makes sense.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to