You want
people to go through *all* open bugs, and decide which ones are blockers
for 3.4.0?
Correct.
How do we avoid duplicating effort (two people reviewing one
bug)?
No easy way except that I would divide up the blocks. I have a
spreadsheet I started to keep track of things.
How do we indicate our decision, by setting the severity to
"blocker"?
And the target to 3.4.0. Though might be best to just update a list for
me to review.
Any particular criteria for deciding what to consider a blocker?
These are hard questions. I typically know'em when I see'em. ;-) If
you see something you think should be moved, you could just mark a
spreadsheet for me to do a second pass.
Has anything like this been attempted before?
Typically before every release, someone on the PMC has run through all
the bugs and moved targets and making sure we are ready to release,
yes. This is the first time I've attempted to do it but I think I'm
being too thorough. It's been very good at getting bugs closed but no
so good on moving us towards a release.
regards,
KAM
