Revision Codes

Each software product and component from DEI has a version number.  You can view SyncDat's version codes by typing "syncdat -v" or "servedat -v".  Be certain to note all version numbers when contacting DEI for technical support.

DEI software versions are designated by a two, three, or five element hierarchial version string.  These value indicate the extent of changes from one release to the next:

Major Revision
Increments to this number indicate substantial changes to the functionality and features of the software.  These may include significant alterations to the interface and there may be compatibility issues between major revisions.  For the purposes of licensing agreements, major revisions are considered new software and may not be included in your support contract.  A major revision number of zero indicates a prototype.

Feature Revision
Feature revisions include new features, enhancements, performance improvements, and functional changes.  Feature revisions are generally cross-compatible, although some configuration adjustment may be necessary.  Customers with support contracts will usually receive access to feature revisions.

Patch Update
If applicable, a patch update reflects bug fixes, minor feature adjustments, and other incremental changes.  Patch updates usually have full backwards and cross-compatibility.  Patch updates are usually available to all customers with active support contracts.

Package Update
DEI software components are packaged together with related software, documentation, installation scripts, and other materials.  If only a non-software component of a package has been changed, or if there has only been a minor software update, then the package update number will be incremented.  When reporting version numbers, remember that the package version is not the same as the versions of individual components.  Starting with SyncDat 1.1, the package update will be a capital letter instead of a number.

Build Type & Build Number
Software under development may be designated as either "a" alpha or "b" beta.  Alpha stage software is functional but incomplete and is known to contain bugs and other functional issues.  Beta stage software is fully functional, but may contain bugs or require feature enhancements.  The build number is incremented for each new build that is released for testing.
Occasionally, you may see other letters at the end of a version string.  Those indicate special builds, usually to address platform or customer specific issues.

For example, a version string of 1.2.3b4 would indicate the fourth beta build of the third patch, of the second feature update of the first version of a software executable.

A version string of 1.2Cb4 would indicate the fourth beta build of the third package update, of the second feature update of the first version of a product package.