..towards Firefox 1.0

Discussion about official Mozilla Firefox builds
Locked
User avatar
Nitin
Moderator
Posts: 3483
Joined: February 27th, 2003, 9:38 pm
Location: San Jose, CA
Contact:

Post by Nitin »

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'.
If you're not using Firefox, you're not surfing the web, you're suffering it.
Join the MZ folding@home team.
User avatar
ehume
Posts: 6743
Joined: November 17th, 2002, 12:33 pm
Location: Princeton, NJ, USA

Post by ehume »

I don't get "Nominated and Blocking." Should it be "Nominated as Blocking"?
Firefox: Sic transit gloria mundi.
User avatar
sensemann
Posts: 755
Joined: February 6th, 2003, 12:29 pm
Location: Dresden, Germany
Contact:

Post by sensemann »

Nominated and Blocking = bugs nominated to block + bugs blocking 1.0
Blocking = only bugs blocking 1.0

sheesh i didn't know it was that hard to understand ;)
: sensemann.com :
.:: Extensions :.
.:: Themes :.
Jacob XP
Posts: 144
Joined: July 20th, 2003, 9:34 am
Location: Denmark
Contact:

Post by Jacob XP »

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

It's not difficult.
Check my blog with new tips to Mozilla Firefox http://www.livejournal.com/users/jacob667
User avatar
sensemann
Posts: 755
Joined: February 6th, 2003, 12:29 pm
Location: Dresden, Germany
Contact:

Post by sensemann »

i darkened the red so it should be "readable" for the colorblind:

Image
sasquatch
Posts: 6022
Joined: November 25th, 2003, 8:56 am

Post by sasquatch »

vfwlkr wrote:
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.
User avatar
Nitin
Moderator
Posts: 3483
Joined: February 27th, 2003, 9:38 pm
Location: San Jose, CA
Contact:

Post by Nitin »

Unbelievable...

I give up.
If you're not using Firefox, you're not surfing the web, you're suffering it.
Join the MZ folding@home team.
User avatar
sensemann
Posts: 755
Joined: February 6th, 2003, 12:29 pm
Location: Dresden, Germany
Contact:

Post by sensemann »

uhm... i don't get it either.

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 :P

updated graphs don't mean dataloss but only data addition!
: sensemann.com :
.:: Extensions :.
.:: Themes :.
sasquatch
Posts: 6022
Joined: November 25th, 2003, 8:56 am

Post by sasquatch »

Ah, I thought those were "official" Mozilla graphs.

Nevermind what I said then.
crafteh
Posts: 469
Joined: August 2nd, 2003, 12:15 pm

Post by crafteh »

i darkened the red so it should be "readable" for the colorblind

Nice, thanks ;)
david5717
Posts: 301
Joined: July 18th, 2003, 7:39 am
Location: Baton Rouge, LA, USA

Post by david5717 »

vfwlkr wrote:Unbelievable...

I give up.

Give up what, insulting posters who may be confused? Good.
Mook
Posts: 1752
Joined: November 7th, 2002, 9:35 pm

Post by Mook »

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...

Ugh, set theory is dancing in my head...
poot.
User avatar
sensemann
Posts: 755
Joined: February 6th, 2003, 12:29 pm
Location: Dresden, Germany
Contact:

Post by sensemann »

ok... once again, here we go:

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.
: sensemann.com :
.:: Extensions :.
.:: Themes :.
Mook
Posts: 1752
Joined: November 7th, 2002, 9:35 pm

Post by Mook »

Ah, okay, thanks :)

So bugs like bug 246382 will not be in the green? (blocking-aviary1.0PR+, fixed-aviary1.0, status:NEW)

I am asking because, as it stands, that bug won't be in Firefox 1.0. But then a search says only 20 bugs are like that.

Again, thanks for explaining - and the pretty pictures :)
poot.
User avatar
sensemann
Posts: 755
Joined: February 6th, 2003, 12:29 pm
Location: Dresden, Germany
Contact:

Post by sensemann »

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.
: sensemann.com :
.:: Extensions :.
.:: Themes :.
Locked