Drivers Update

Friday March 29th, 2002

The Status Reports was updated, and included some information on what are up to, and what's coming up:

" approved checkins for over 240 bugs this last week. We've taken a few more big-ticket items and have a couple to go. drivers will be ramping down this next week and actively soliciting fixes that we need to branch and have a Release Candidate 1 sometime (hopefully) late next week. We need to get RC1 out there quickly and get feedback on all the changes we've taken since 0.9.9 and at the same time we need the release to stand up so that users will put enough hours on it to give meaningful feedback. Please help us to get the builds into good shape over this next week with particular attention to recent regressions and topcrash+ bugs."

#9 Re: Is calling it RC1 a big and unnecessary PR ris

by Kovu <>

Friday March 29th, 2002 7:25 PM

You are replying to this message

I might note that the differences between Windows XP RC1 and the final release were fairly significant.

Honestly, no one's going to care if RC1 is a little buggy, it's light years past the Netscape 6 release, which was bashed very badly by just about everybody.

I might also note that based on the bad reviews of Netscape 6 PR1, I had my publisher yank "Netscape 6 For Dummies".

I guess I'm arguing both sides here. It IS important to make sure RC1 is a good, stable, usable program. By definition, a "release candidate" is actually a "candidate for release" and is therefore something that the releasing body supposedly thinks is worth a release. The RC stage of software is really the last chance for surprise monster bugs (like in Starship Troopers).

I do think that if 1.0 goes to RC4 or beyond, that will prove that RC1 was anything but a real "candidate for release."