Quote:

The "b" stands for BETA...


From Andrew's post: "We are using the "b" to indicate that some files have changed since the build 316 release on April 19."

I do realize that a new patch is usually noted as being considered beta. But seems like that advisory is rarely, if ever, removed. So we cautious types, who are reluctant to install a beta, are never sure when the patch is considered "production." Usually, the beta-notification sticks until the next patch. Which is then also labeled as beta.

Maybe that's the point? Every new patch is, and remains, beta *until* it's replaced by the next patch? So if the entire user base is testing a beta, what do the beta testers do...? <= note smiley please.

-Ron

(...who, despite appearances, usually installs new patches soon as they're posted... Hence my initial concern about keeping build designations unique.)