What is an alpha or beta release?

2013-05-31T12:01:13Z

Moc: /* e107 releases */

{{Handbook open|Frequently Asked Questions Section of [[Help:e107 Handbook|e107 handbook]]}}

=== Alpha ===
The alpha phase of the release life cycle is the first phase to begin [http://en.wikipedia.org/wiki/Software_testing software testing] (alpha is the first letter of the [http://en.wikipedia.org/wiki/Greek_alphabet Greek alphabet], used as the number 1). In this phase, developers generally test the software using [http://en.wikipedia.org/wiki/White-box_testing white box techniques]. Additional validation is then performed using [http://en.wikipedia.org/wiki/Black-box_testing black box] or [http://en.wikipedia.org/wiki/Grey_box_testing#Grey_box_testing gray box] techniques, by another [http://en.wikipedia.org/wiki/Software_testing testing team]. Moving to black box testing inside the organization is known as ''alpha release''.

Alpha software can be unstable and could cause crashes or data loss. External availability of alpha software is uncommon in [http://en.wikipedia.org/wiki/Proprietary_software proprietary software]. However, [http://en.wikipedia.org/wiki/FOSS open source software], in particular, often have publicly available alpha versions, often distributed as the raw [http://en.wikipedia.org/wiki/Source_code source code] of the software. The alpha phase usually ends with a [http://en.wikipedia.org/wiki/Freeze_(software_engineering) "feature freeze"], indicating that no more features will be added to the software. At this time, the software is said to be [http://en.wikipedia.org/wiki/Feature_complete "feature complete"].

=== 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 [http://en.wikipedia.org/wiki/Feature_complete feature complete]. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating [http://en.wikipedia.org/wiki/Usability_testing 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 [http://en.wikipedia.org/wiki/Perpetual_beta "perpetual beta"]—where new features and functionality are continually added to the software without establishing a firm "final" release.

=== e107 releases ===
Currently (May/June 2013), e107 v2 is in Alpha stage; it is intended for experienced e107 users or those who are interested to see the development progress. '''It is NOT intended for production use on live websites!'''.

[[Help:FAQ_on_e107|Back to FAQ]]
[[Category:FAQ]]
{{Handbook close}}

e107 Wiki - New pages [en]

What is an alpha or beta release?