Are Betas Taking On Lives of Their Own?
Ant writes "CNET News.com's Paul Festa thinks the final stage of software development, beta versions, are taking on a life of their own, as companies tinker endlessly with their products in public according to a recent article. Google is one of the companies that keep using "beta" term for years for its products."
ICQ was like that (I dont know if it still is, I haven't used it for years.). They'd just be in permanent beta. What a cop out. Grow a set and put a "release" stamp on it, bugs and all. Works for Microsoft.
I'm Rick James with mod points biatch!
Now, we have the new perpetual beta. Any company can, with a wave of the magic wand, make itself blameless when its software doesn't work. "But it's in beta!" they gleefully shout when you tell them about something that doesn't work correctly. "Refer it to our testing team, who will ignore your report."
Shutting down free speech with violence isn't fighting fascism. It IS fascism!
It's a simple case of fear of commitment (or litigation). If a product is beta, you don't have to really support it, and if it breaks it's really no big deal. It is, after all, a beta version.
Once you make the jump to release versions then suddenly everything has to run (nearly) perfectly and any issues need to be properly dealt with. Perpetual beta has it's advantages in that you simple don't deal with these problems. Or you don't deal with them formally, but you do fix them.
Google News is stuck in beta because Google can and will be sued the instant they start trying to make money (via text ads or something) off other sites headlines and stories.
I agree that selling software actually labeled as beta is a bad idea, but don't we already pay for software that require constant patching, such as the latest release versions of Windows, Microsoft Office, and nearly all of the latest games? Does release software even live up to the quality expected?
.sig: Open Source, Open Mind
and
What little training I had seemed to involve code existing in four stages of development, and beta was the second:
Alpha: the phase in the development cycle where code first comes into being. Subsystems are being built, and testing takes place on the that (subsystem) level.
Beta: the phase in the cycle where all subsystems are nominally in place, and testing occurs on the system level; not everything works, and features may be added, but we're looking at the whole code.
Final: features are locked down, the system is tested in the form it intends to be released. I believe, under the influence of someone like Microsoft, this is now referred to as "Release Candidate" stage.
Released: The software has been distributed.
On the other hand, this article implies another notion of software development stages, one that I see applied rather frequently:
Alpha: Testing done in house.
Beta: Product released to a group of testers who aren't in-house QA specialists.
So does someone have the answer? What the hell do these terms mean, and are they useful any more?
Beta prevents the need for support but allows you to sell/release your product. This is a dream as it prevents those damn leeches called "consumers" from harassing them.