| |
|
|
|
 |
|
|
 |
|
| |
Beta Test Releases
On a regular basis, we release alpha and beta ClarkConnect releases.
These test releases are an excellent way for users and developers to experiment
with the latest features.
Word of Caution
Familiarity with the command-line environment is a requirement for installing
a test build. Why? Manipulating configuration files might be required
for enabling some of the leading edge features.
|
|
 |
Please review the release notes of each test release. Some releases
are only for developers and not usable by an end user. On the other hand,
some releases will be one or two bug fixes away from completion.
|
 |
|
Alpha vs. Beta vs. Release Candidate
The definitions of alpha, beta and release
candidate depend on who you are talking to. For ClarkConnect we define these terms as follows...
| Alpha |
- Alphas should not be running in a production environment.
- Many core features are incomplete or untested.
- Upgrading to the final release is not guaranteed.
|
| Beta |
- Betas can be running in less critical environments (personal home server)
- Most of the features are complete and in working order.
- Upgrading to the final release is (usually) painless.
|
| Release Candidate |
- Release candidates can be running in a production environment.
- The software is feature complete with no known bugs.
- Upgrading to the final release is guaranteed.
|
|
Release Schedule
Please review the roadmap for release
dates more than 6 months away. The following release dates pertain to
the immediate future only. Keep in mind, these are estimated dates only.
We may hit a few roadblocks along the way!
|
|
|
