Comment 2 for bug 376174

Hi Curtis,

I'm glad you're tackling this problem, you've been a bug-closing-machine lately :)

First, in reply to your ideas:

> * Add a timeline of milestones and releases (tracked by separate bugs).

Great idea. I guess this would just be a view of the series you're looking at.

> * Use the milestone widget to create a new milestone and update the
> milestone and release table.

Yes yes yes! :)

> * Maybe include the number of bugs and blueprints each milestone/release has.

If I where daydreaming, I'd want to see the number of bugs, but grouped by status (ie. 12 Triaged, 40 fix committed)

> * Maybe show a sparkline of the branch.

Pretty easy to do once we get the API for it in place (it's a view right now, and has XSS issues)

> * We need to make the role of driver clear. There is a bug about the project owner
> is not a driver, which is not true. Owners are drivers, and they may delegate the
> responsibility to other users.

Are there drivers per series?
Either way, I think we should show both the owner and the driver, if they're different people.

As for the screenshot, a few thoughts:
- "Expected" column with no dates should probably be an action: "_Set_(i)"
- "Released" column with no release, "_Release now_ (+)"?
- How about showing bug stats per milestone as well? (again, 12 Triaged, 40 fix committed)
- Does it matter who created the branch? do we need text? maybe show the revno the branch is at, and last commit date?
- Why does it say "link to a branch" when there's already a branch? can you link to multiple branches?

Phew, that was longer than expected. Great work so far, let's nail this!