..towards Firefox 1.0

RichCorb · Post by **RichCorb** » August 17th, 2004, 12:25 am

amano wrote:Thanks for posting 2 weeks old information as "Update !". The usenet post is from August 2nd!

Was never posted on mz front page so was an update to me!

sasquatch · Post by **sasquatch** » August 17th, 2004, 11:13 am

sensemann wrote:more bugs "fixed" than "to be fixed" today - for the first time. hooray

I hate to pee on your cornpops, but if that was in your car, you'd be pretty upset. Imagine:

"Today, we finally have the number of things we have fixed on your car is greater than the number of things we still have to fix. What, aren't you happy?"

Just funnin' ya.

;-)

MORA · Post by **MORA** » August 17th, 2004, 11:43 am

sasquatch wrote:I hate to pee on your cornpops, but if that was in your car, you'd be pretty upset. Imagine:

"Today, we finally have the number of things we have fixed on your car is greater than the number of things we still have to fix. What, aren't you happy?"

Just funnin' ya.

Do you drive a nightly build of a pre-release of the next car model?

michaell522 · Post by **michaell522** » August 17th, 2004, 11:52 am

Something else to point out is that "FIXED" status refers to trunk builds, and of course Firefox is on a branch. To get the right numbers, you should actually be checking for the fixed-aviary1.0 keyword that indicates that the bug is fixed on the branch, rather than the "FIXED" status which means it's fixed on the trunk. If you do it that way, there are a few more blockers to count. Also, it looks like those counts are for Firefox bugs only - there are quite a few other bugs which are blockers too.

blocking1.0+ and not fixed-aviary
blocking1.0+ and fixed-aviary
nominated for 1.0

Flinx · Post by **Flinx** » August 18th, 2004, 6:07 pm

michaell wrote:blocking1.0+ and not fixed-aviary

Ack! That is a lot of bugs.

Mook · Post by **Mook** » August 18th, 2004, 7:10 pm

michaell:
Actually, some FIXED bugs are also fixed on the branch - for example, bug 240527 (first resolved fixed bug in the list) - see lxr. As far as I can tell, there is no consistent way of checking...

michaell522 · Post by **michaell522** » August 19th, 2004, 2:51 am

Mook: yeah, those bugs should have the fixed-aviary1.0 keyword, but not all of them do. I went through and added it to a bunch of them. That one is one of the ones I wasn't sure of. From your lxr link, it obviously is on the branch, so I've added the keyword now...

sensemann · Post by **sensemann** » August 19th, 2004, 10:31 am

it's not really cool for the graph, but I've updated my bugzilla queries and will be using the better ones from now on.

michaell522 · Post by **michaell522** » August 19th, 2004, 11:20 am

sensemann wrote:it's not really cool for the graph, but I've updated my bugzilla queries and will be using the better ones from now on.

oops... sorry to mess up your graph

The different queries only makes a correction of a few bugs, except for the "FIXED" query, which before was including 1.0PR blockers marked "fixed", and now it isn't.

It's not really possible to make a "good" query which includes both. If it helps, when I ran a query for fixed 1.0PR blockers and then took out the ones that are also 1.0 blockers, it came up with 54 bugs. That's not really a useful figure because of the keyword thing, but adding that on would make your green line figure more consistent with the previous green line figures... whatever you want to do...

Tim R · Post by **Tim R** » August 19th, 2004, 11:57 am

Perhaps you should insert some kind of marker at the point where you updated the queries? I almost had a heart-attack when I saw the nice green line take such a dive.

zachariah · Post by **zachariah** » August 19th, 2004, 2:25 pm

you just need two green lines -- one for the new and one for the old

poningru · Post by **poningru** » August 19th, 2004, 5:38 pm

Jees luise scared the crap out of me.

prandal · Post by **prandal** » August 20th, 2004, 3:34 am

There's a new Roadmap out.

1.0 PR is now expected around August 30th, RC-1 Sept 20th, RC-2 Oct 4th, and 1.0 on Oct 11th.

PiTaGoRaS · Post by **PiTaGoRaS** » August 20th, 2004, 4:09 am

I've just started the recent installed trunk 2004081907 and the autoupdate tells me to update to 1.0 Preview Release! But when I press Next all the components give error on installing...

UPDATE:
Update Required screen
Error screen

Powersurge · Post by **Powersurge** » August 20th, 2004, 5:25 am

PiTaGoRaS wrote:I've just started the recent installed trunk 2004081907 and the autoupdate tells me to update to 1.0 Preview Release! But when I press Next all the components give error on installing...

That's been happening for some days, probably intended to test the update detection function. As there is no 1.0PR so far (it has just been rescheduled for Aug 30), it is of course not possible to update to it.