Release Notes

Introduction

This page lists the firmware and software releases that have been made by the DAT Group. Links to notes describing each release can be found below. The method for building and releasing is described in DAT Build and Release system.

Regression testing

Prior to declaring a release of a DAT project, it shall undergo a series of regression tests. These tests are described with the corresponding project.

Enumeration

The standard policy is to use Major, Minor, and Revision numbers. Increasing the Major version number signifies a non-backwardly compatible change to the API, a Minor version number change signifies a backwardly compatible change to the API, and a Revision number change signifies an implementation (not an interface) change.

Release numbers are built from the Major, Minor and Revision numbers. The standard syntax is MM-mm-rr, where 'M' is a Major release number digit, 'm' is a minor release number digit and 'r' is a revision number digit. This string is also used to tag the corresponding software in the code (svn) repository. Release numbers are sometimes referred to in the format M.m.r, in which leading zeros are omitted.

Sometimes it is useful to declare release candidates. This is signified by appending the term rc<N> to the standard release number, where <N> is a sequential count that starts with 1 (one) for each release. From the standpoint of the code, the candidate is identical to the actual release, so candidates and actual releases have identical release number values embedded in them. Release candidates are not meant to ever be distributed to users.

Releases

The following releases have been produced:

Compatibility

The following table shows the compatibility between released projects:
The method to show this needs work...