For those of you who are anxiously awaiting the first release candidate of Firefox 3 (like me) it looks like the wait will soon be over. Checking the latest RC1 blockers (bugs that are currently blocking the release candidate) shows only 4 remaining bugs to squash before RC1 can get itself out of the trunk. And on the forum today, as some of you who followed my previous post may have already read, it was stated on the last nightly build topic that all blockers should be cleared up by tonight.
This means that RC1 can now come out of the oven and head to “build” and all the required QA testing from there. If all goes right I’m predicting we should see RC1 released sometime late next week (which is an educated guess on my part of course).
I’d still bet a nickle that I’m right though.
Of course this will mean I’ll have to find and install all my extensions again but what the heck, it isn’t the first time I’ve had to do that. In fact it’s not even the 18th time I’ve had to do that while testing the nightly builds. However, it should be the last time I have to do this right through the final release date..or at least that’s the grand scheme anyway. 
Technorati Tags: Firefox 3, Firefox 3 RC1
Ooh, RC1. I hope so!
Have you found that the beta 5 release gets the same memory bleed that FF2 was getting? I’m having to force-quit a whole heck of a lot more than I like lately.
Now that I’ve found your blog, I can stalk you as well as Sixty. Heh.
Hi Rachael,
Welcome to my end of town.
Beta 5 still had a ton of bugs in it and the XPCOM memory recycler wasn’t fully implemented yet. Neither was the “Places” (Organize Bookmarks/Library) SQLite database features. There were problems with Java script and Flash etc.
I’ve been running the (trunk) nightly builds (Minefield) since the late Alpha’s and as of yesterday the last bugs blocking RC1 were squashed. I’d expect RC1 to be released late next week by the look of the “Release and Tracking Schedule”. And yes, the latest trunk builds have been very well behaved as far as memory use and reclamation is concerned, a far cry from beta 5. I’m lovin’ it.
More than you needed to know? That’s my biggest failing–too damn wordy. Comes from writing too many operational procedures.
I like your Gravatar image BTW.
Oh, I’m glad to hear that RC1 is much much better. I love Firefox dearly and it pains me every time I force it to shut down.
Of course, I’m all sensitive and crap, even about my favorite techy things. HAHA.
My biggest failing is ALSO being too damn wordy! OMG! We must be best friends!! I’ve written a very small number of manuals myself, so I totally understand the almost impulsive need to use bullet points to explain negligible things to friends of mine who happen to express curiosity about something.
Unless that doesn’t happen to you. In which case, let’s talk about our nefarious plot.
Hey Rachael,
Bullet points galore! I also have this god awful obsession for using the word “Ensure” start a sentence:
“Ensure you check this” and “Ensure you click that” or “Ensure that other thing loads” etc, etc.
Okay…so I thought of a few things already but on second thought; immediately dismissed as being too nasty. To wit:
> Change “index.php” to “index.html” and stick in a meta redirect to the “Webkinz Pets” site.
> Change just one digit in his Akismet “key” to something else…mua-ha-ha-ha!
> Add a line into his “.htaccess” file that specifies only users with my IP address or your IP address can log in. (see evil laugh above).
But I figured all the above were just drastic. How about Digg-ing and Stumbling several posts and when his site grinds to a halt from the massive traffic spike you can rescue his rear end by installing “WP Super Cache”.
Do we need to do this by email on the off chance he might actually read this?