This page is dedicated to software projects under development by Red Mars Consulting. The
projects listed will be at various stages of completion. The information below explains
the development and versioning. If you want to skip the gory details and get to the
projects, quick links are available on this page.
Alpha products are considered to be in the very early stages of development.
You may use them but do so at your own risk and we'd adivsed for them to not
be run in a production environment.
Beta products are considered feature complete and near ready for release.
Beta products may still contain some bugs and it is the intention of this
phase to identify and rectify those bugs.
Release Candidate products are ready for release and are considered near
final. The purpose of a Release Candidate is to identify and eliminate major
Products marked as Final are fully tested and considered available for
general use. They are feature complete and only bug fixes will be applied to
How our versioning works
To help identify what stage our products are in we use the following naming
and numbering standard.
An Alpha release is identified by a dot release. i.e. 0.1 When a new
features are released the dot release is incremented i.e. 0.2. Alpha Bug
fixes are identified as sub releases. For example 1.2.1 is bug fix 1 for
Alpha version 1.2.
A Beta release is identified at the whole number level i.e. 1.0b or 2.0b.
Bug fixes at the Beta stage are identified as a sub number after the b. For
instance 1.0b1 is the first bug fix.
A Release candidate is identified as such 1.0rc1. Which is the first release
candidate for 1.0. If further release candidates are required due to major
bugs then they are sequential. i.e. 1.0rc2.
The Final product is identified as simple the whole release number with no
modifications. i.e. 1.0. Bug Fixes at the Final stage are identified like
this 1.0.4. This example identifies there has been 4 bug fix releases since
the Final 1.0 release.