Skip to content

Latest commit

 

History

History
executable file
·
53 lines (46 loc) · 2.44 KB

COMPATIBILITY_MATRIX.markdown

File metadata and controls

executable file
·
53 lines (46 loc) · 2.44 KB

Compatibility Matrix

In general reef aims to maintain backwards binary compatibility between client and server versions within the same minor revision. (Minor revision is middle number in the version number). So all 0.4.0 clients should work with all 0.4.x servers, all 0.5.x servers should be compatible with older 0.5.x clients etc.

The one big caveat is with functionality introduced inside a minor revision. In many cases (but not all) new functionality in the client requires new code in the server so usually new functionality requires that both the server and client be updated together. If the applications don't make use of newly introduced functionality a newer client will work with an older server. We will try to mark which features require updated server components here and in the change log.

Client/Server0.3.x0.4.00.4.10.4.20.4.3 0.4.40.4.50.4.60.4.7
0.3.xOK--------
0.4.0-OKOKOKOKOKOKOKOK*3
0.4.1-OK*1OKOKOKOKOKOKOK*3
0.4.2-OK*1OKOKOKOKOKOKOK*3
0.4.3-OK*1OKOKOKOKOKOKOK*3
0.4.4-OK*1OKOKOKOKOKOKOK*3
0.4.5-OK*1OKOKOKOKOKOKOK*3
0.4.6-OK*1OKOKOKOKOKOKOK*3
0.4.7-OK*1OK*2OK*2OK*2OK*2OK*2OK*2OK

Caveats:

  1. Setpoint executions with strings and command error responses will be ignored
  2. Servers before 0.4.7 will ignore client and application version information.
  3. Clients previous to 0.4.7 will be considered to have "unknown" client and application version.