I think you should rather be using the fields for targeting bugs at specific versions to keep track of stuff that still needs doing.
>From the outside, it's impossible to know if a bug assigned to you means - someone else can pick it up - you already have a specific idea, but haven't coded it yet - you have a patch and you haven't bothered to commit it -- Noel. Greg Brown wrote: > That is just my way of keeping them on our radar. It shouldn't be > considered a strict assignment. Developers should feel free to review > any issues assigned to either me or Todd to see if they would like to > work on something. > > > On Aug 6, 2009, at 3:22 AM, Niclas Hedhman wrote: > >> Gang, >> >> I think you guys are a bit too quick to 'assign' the respective >> issues. Leave them unassigned until you are about to start working on >> them. I see many that are assigned to either Greg or Todd, but could >> equally be picked up by anyone else. So, Greg/Todd, unassign the ones >> that are not on your 'immediate list of the day'... >> >> >> Cheers >> -- >> Niclas Hedhman, Software Developer >> http://www.qi4j.org - New Energy for Java >> >> I live here; http://tinyurl.com/2qq9er >> I work here; http://tinyurl.com/2ymelc >> I relax here; http://tinyurl.com/2cgsug >
