SecondLife has released the twelfth Release Candidate for version 1.20 of their viewer software, and while I’d love to be able to simply point out the good things in this RC instead I’m going to have to take them to task for changing what is the pretty universal stages of software design and testing. I’ve spoken to Peng about it and he’s pretty dumsquizzled that they’re calling what are clearly beta versions as “Release Candidates.” I did some searching on my own and found two examples of how software testing should go.
I know that Wikipedia isn’t as reliable a source as the Encyclopedia Britannica was, but from checking out other sites I suspect they’re pretty on target, even if some citations are needed.
Before shipping the final version of software, alpha and beta testing are often done additionally:
- Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing
- Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.
And yes, a Release Candidate should be software that the devs think may just be ready for prime time and need testers to make sure there are no major bugs that absolutely have to be fixed before release.
Even MySQL, a software developer that’s been around since the mid-90’s agrees with these definitions.
Alpha Release
Alpha is for preview purposes only.
Beta release
Beta releases are appropriate for use with new development. Within beta releases, the features and compatibility should remain consistent. However beta releases may contain numerous and major unaddressed bugs.
Release Candidate (aka Gamma) release
Release Candidate binaries, also known as Gamma releases, are believed stable, having passed all of MySQL’s internal testing, and with all known fatal runtime bugs fixed. However this release has not been in widespread use long enough to know for sure that all bugs have been identified.
Generally Available (aka Production) release
Generally Available (GA), also know as Production releases, are stable, having successfully passed through all earlier release stages and believed to be reliable, free of serious bugs, and suitable for use in production systems
Needless to say when SecondLife announced yet another in a series of Release Candidates I had to ask them what was going on.
TWELVE Release candidates? How about releasing a viewer and working on Dazzle or something for the next version. In all honesty, if it takes you twelve times to get a viewer out of beta stage I doubt you’re really trying at all.
Yes, I’m glad to be able to wear a non-prim skirt again. Yes, I like what I’m seeing, but come on. Twelve RCs is pretty ridiculous.
As I suspected some over grown kid had to flame me.
@8: It’s rather obvious you never developed software (and no, 10 lines of Basic don’t count).
Luckily someone injected a little more reason to my complaint.
TWELVE release candidates?!
Look, I’m sure there are quite a few very competent code monkeys over there in Linden land, but to anyone who has ever worked with a team of developers this screams out “Project Mismanagement”.
A “Release Candidate” is suppose to be considered “Ready for Release” baring any unforeseen major issues. This client should NEVER have come out of beta.
If the project manager can’t tell the difference between beta and RC then perhaps the Lindens need to start scouting for a new team leader.
That being said, I have yet to see any performance or usability improvements over the current gold client. This is like going from XP to Vista – it “looks” prettier, but it performs worse.
I hate to be all negative like this – I’ve been on SL a LONG time and I truly WANT to enjoy it. But honestly, this new client feels like you guys are treading water – that you’ve already hit some sort of ceiling and your users have no “wiz bang neato” features to look forward to.
How about throwing your user base a bone – open up the vertical area to 4096m for building, increase the outdated sim prim limit, allow users to create prims larger than 10m, allow greater flexibility in altering avatar meshes. These are things that will IMPROVE the user experience instead of just parading an endless stream of RC’s that are actually Beta’s in disguise.
Ramzi Linden gave us an official response.
@8, @11- Yes there has been a lot of 1.20 Release Candidates, huh!
The (technical language) reason is that we rebranched this candidate from the code-trunk at RC7, which means it was based on a somewhat different/improved codebase than RC0. (You may recall it was 1.20.7 that introduced a very large slew of new fixes, and even some new features.. we usually don’t do this.) Our intention in this unusual move was to utilize the benefits of some major stability work that hadn’t been ready from RC0 to RC6.
The faster answer is: We were not satisfied with the stability of RC0 – RC6, so we redoubled our efforts in a second extended cycle. Hence the reason for twice as long. As JetZep and Catten said, it means we had time to do many more bugfixes. I hope the result is a better version 1.20, which everybody wants!
In other words RC7 wasn’t even an RC, but a new branch of betas. I just wish they had called it what it was.
Now if only we could know that a final release was coming soon, but with twelve release candidates I’ve learned to never trust a SecondLife RC as a real RC. I’m thinking of going back to the official release rather than downloading yet another so called Release Candidate, especially since I have to apply Torley’s Windlight settings as well as a different skin to get rid of ugly the Dazzle Blue. And they wonder why their users still aren’t completely thrilled with having to spend money on monthly subscriptions, let alone tier fees.
I meant to post this last night but now I’m glad I waited until this morning. With this post I’m calling a full lid for the 4th of July holiday. Peng has some links he meant to post yesterday but was unable to after spending too much time on his feat assisting a roomie who had surgery last week. and I told him to take today off for the holiday. He’s got a bunch of links to post tomorrow, and I told him he
has to post a link to where you can see
Boston’s fireworks online tomorrow for those who don’t join TV’s
Craig Ferguson, the (fairly) new American citizen, for the
broadcast tonight from the Hatch Shell.