TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Where I work, we have several desegnations for software. Alpha, which is
before the Beta release, and assumed to be full of bugs. Then there is
Beta, the version we release to developers, testers and those who need
software to design product tests. We requires this nomenclature.
Incidentally, we also occasionally release Pre-Alpha which is a potential
computer killer. Then the ever popular Pre-Beta, which is a slightly less
buggy version of the Post-Alpha release. Whew...I understand why this is so
hard.
Personally, I would call it Beta, then add the version number. Add a short
disclaimer to tell the user that some functionality is either undergoing
revisions or is not implimented yet.
If your audience for the software release is people like engineers,
testers, etc., then they will understand what Beta indicates. Never call it
Bug Free, as there is no such thing, really. Even programs like MS Office
have their problems.
