Release Information

DDS Community Edition Releases

DDS Community Edition releases are denoted by either a two or three component release identification number.

Major.Minor Community Releases

These releases correspond to the DDS Community Edition roadmap milestone major (e.g. Major.0) or minor (Major.Minor) releases. The timing of these releases is set by the DDS Community Edition roadmap.

Any Major.Minor release of  DDS Community Edition will be binary compatible with the corresponding version (and any subsequent maintenance releases) of the supported OpenSplice DDS Editions (for content that is common across the editions). A comparison of the edition contents can be seen here.

Major.Minor.Date Incremental Community Releases

Subsequent DDS Community Edition releases are made on an approximately monthly schedule until the next scheduled Major.Minor release.

These have release identifiers in the format Major.Minor.Date. The Major and Minor numbers track the values for the preceding supported  DDS Community Edition releases. The Date of the DDS Community Edition release will be the date that the release is made on. Each release of DDS Community Edition will contain all new features and bug fixes that have been made since the previous release. This means that, in terms of possibly changes to content, each incremental DDS Community Edition release should be considered as a beta for the next Minor or Major release (depending on which is scheduled).

Compatibility Between Releases

Depending on whether the next scheduled release is a Major or Minor then the level of compatibility with the preceding DDS Community Edition release will be as follows:

Next scheduled Major.Minor release changes Major number

  • APIs of DDS C9ommunity Edition may have been changed
  • Network format may have been changed
  • API implementation may have been changed. Meaning: preprocessor (idlpp and/or ospldcg) output may have been changed
  • Regeneration of any preprocessor output code is required.
  • System wide (i.e. all nodes) runtime updates must be applied!
  • Customers may need to make modifications to application source code
  • Customer application code must be recompiled.

Example: the transition of DDS Community Edition 4.x.x to DDS Community Edition 5.x.x

Next scheduled Major.Minor release changes Minor number

  • APIs of DDS Community Edition have not changed
  • Network format may have been changed
  • API implementation may have been changed. Meaning: preprocessor (idlpp and/or ospldcg) output may have been changed
  • Regeneration of any preprocessor code is required.
  • System wide (i.e. all nodes) runtime updates must be applied!
  • Customer application code must be recompiled.

Example: the transition of DDS Community Edition 4.1.x to DDS Community Edition  4.2.x or DDS Community Edition 4.1.080203 to DDS Community Edition 4.1.080407

NOTE: These are the minimum compatibility implications for changing upgrading between any two DDS Community Edition versions.

Obtaining Binary Releases of DDS Community Edition

Pre-built binaries of the latest DDS Community Edition release for Linux are available from the downloads page without support.

If you require supported binary releases for this or other platforms please see the details of the other Vortex OpenSplice editions or contact the PrismTech Customer Response Centre.

If you would like to contribute a binary release build of DDS Community Edition then please see this page.

Obtaining Source Releases of DDS Community Edition

Source Downloads

Source downloads are available for the DDS Community Edition releases on the Download Page.

Please see the Building DDS Community Edition page for details of how to build and install these source releases.

Source Repository Access

Please see the page Repository Access for details of how to get access to the Community Edition development source repository directly.