crafteh wrote:Maybe you could change the colors of the blocking 1.0, and the blocking 1.0 and FIXED to be more friendly to the colorblind. I can't tell which is which in the graph! D: Maybe a light and a dark color would be good!
red and green is nicer.
green= good
red= bad
If you are colourblind just look at the graph. The line that is rising is about the number of bugs fixed. The other one is blocking bugs. The dotted line is nominated and blocking 1.0
sasquatch wrote:plus it would keep a "history" of the progress)
Could we get dumber and dumberer?
Place a scale at the date you want, and the graph to the left is your 'history of progress'.
No, I mean have each picture as a snapshot in time.
That way, when the developers decide to rewrite history (wipe out a bunch of blockers, for example), we will know they were there at one point in time.
say there were about 199 blocking bugs on the 22nd of July - you will always see there were 199 of them on the 22nd of July in my graphs,, even when i update the graph and devs decide to move bugs. noone will ever be able to "rewrite" the history of my graph
updated graphs don't mean dataloss but only data addition!
Hmm, am I reading the graphs right?
blue = (blocking?) union (blocking+)
red = (blocking+)
green = (blocking+) intersection (fixed-aviary)
Or is the green (blocking+) intersection (resolved: fixed)? (In which case it wouldn't be tracking what's actually fixed for 1.0, which means it won't make sense in conjuction with the flags set)
Oh, and if the green is a subset of the red (if you're doing intersection), wouldn't the pie chart not make sense? Unless the red is (blocking+) intersection (no keyword fixed-aviary) or maybe (blocking+) intersection (not resolved: fixed) or something...
RED are Browser-Firefox bugs with the blocking-aviary1.0PR or blocking-aviary1.0 flag set to + which are UNCONFIRMED, NEW, ASSIGEND or REOPENED.
GREEN are Browser-Firefox bugs with the blocking-aviary1.0PR or blocking-aviary1.0 flag set to + and having been FIXED (so they're not a subset of the reds).
FINALLY the blue line indicated something like the "total" number of bugs blocking 1.0. It's RED + bugs with blocking-aviary1.0PR or blocking-aviary1.0 flag set to ?.
Check the Bugzilla Query in Peter's daily build threads - i'm using hte same.
yup, you're right. They won't appear in green. those bugs are a bit "extra" anyways since they mostly result in backed out code for the aviary branch that is still causing trouble on the trunk and will have to be fixed still, though it won't affect the ff 1.0 release.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.