On 24 May 2011 20:31, Zach Pfeffer zach.pfeffer@linaro.org wrote:
My solution to this is to file a bug and link it to the BP if it needs more than one line of info. This seems to work because anything that needs more than one line is probably not 2 days of work - which is what should go in the BP (which is my understanding). The bugs get picked up by status, so it all seems to work out.
I found trying to link bugs to blueprints didn't work very well for me/qemu, so I'm avoiding it this cycle: * the linked bugs are listed in a different part of the blueprint page to the work items, so the todo list for the blueprint isn't in one convenient list * you can't mark a bug as 'postponed' to the next cycle (short of marking it wontfix) so you have to just unlink it, which means the entry just vanishes from the blueprint and status * also as you imply it's easy for a single linked bug to hide a big chunk of non-broken-down work
But I think the underlying thing I was hitting was that my bugs were generally user-reported ones that came in randomly during the cycle, so often only tenuously connected to the blueprints anyway. So linking bugs might well work better for the approach you suggest.
-- PMM