well for me i would not use anything beta or RC on my main computer without a way to restore back to a clean state in case something gets messed up i'v beta tested before and it's easy to brick your pc especially security software one bad definition update and if it finds system files bad and you let it clean them then bam your pc don't boot know more lol
definition of Beta and Release candidate software from wikipedia
http://en.wikipedia.org/wiki/Software_release_life_cycle
Beta
Beta (named after the second letter of the Greek alphabet) is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically
the first time that the software is available outside of the organization that developed it.
The users of a beta version are called beta testers. They are usually customers or prospective customers
of the organization that develops the software, willing to test the software without charge, often receiving
the final software free of charge or for a reduced price. Beta version software is often useful for demonstrations
and previews within an organization and to prospective customers. Some developers refer to this stage as a preview,
prototype, technical preview (TP), or early access. Some software is kept in perpetual beta—where new features and
functionality are continually added to the software without establishing a firm "final" release.
Release candidate
A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities.
Some users disparagingly refer to release candidates and even final "point oh" releases as "gamma test" software,
suggesting that the developer has chosen to use its customers to test software that is not truly ready for general release.
Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product.
Beta testing is conducted in client's or customer's location and to test the software from users perspective.
