.. include:: vars.rst

.. |br| raw:: html

   <br />

.. _section-release-notes:

Release Notes
=============

Supported Platforms
-------------------
|CDS| is supported on the platforms listed in
:numref:`TableSupportedPlatforms`. No custom platforms are supported.

.. list-table:: Supported Platforms in 6.0.1
    :name: TableSupportedPlatforms
    :widths: 10 90
    :header-rows: 1

    * - Platform
      - Operating System
    *
      - Linux®
      - All Linux platforms on x86/x64 CPUs in the |CORE_RELNOTES| with the 
        same version number, except SUSE® Enterprise Linux and
        Wind River® Linux 7.
    *
      - macOS®
      - All macOS platforms in the |CORE_RELNOTES| with the same version 
        number.
    *
      - Windows®
      - All Windows platforms in the |CORE_RELNOTES| with the same version 
        number.

Compatibility
-------------
For backward compatibility information between |CDS| 6.0.1 and
previous releases, please see the *Migration Guide* on the
`RTI Community portal <https://community.rti.com/Documentation/>`_.

Connext DDS Compatibility
^^^^^^^^^^^^^^^^^^^^^^^^^
|CDS| can be used to provide discovery for applications built with
*RTI Connext DDS*, except as noted below.

- Starting in *RTI Connext DDS* 5.1.0, the default ``message_size_max`` for the
  UDPv4, UDPv6, TCP, Secure WAN, and shared-memory transports changed to provide
  better out-of-the-box performance. |CDS| also uses the new value for
  ``message_size_max``. Consequently, |CDS| is not out-of-the-box compatible
  with applications running older versions of |CONNEXT|. Please see the
  |CORE_RELNOTES| for instructions on how to
  resolve this compatibility issue with older |CONNEXT| applications.

What's New in 6.0.1
-------------------

New platforms
^^^^^^^^^^^^^
|CDS| now includes support for these platforms:

- macOS 10.14 (x64)
- Red Hat® Enterprise Linux 8 (x64)
- Windows 10 (x86, x64) with Visual Studio® 2019
- Windows Server 2016 (x86, x64) with Visual Studio 2019

For more information on these platforms, see the |CORE_PLATNOTES|.

Removed platforms
^^^^^^^^^^^^^^^^^

These platforms are no longer supported:

- macOS 10.11
- Windows 7
- Windows Server 2008 R2





What's Fixed in 6.0.1
---------------------

|CDS_Heading| executable did not log build ID for DDS libraries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In |CONNEXT| 6.0, the DomainParticipantFactory initialization didn't 
appear anywhere in the logging generated by |CDS| for any verbosity 
level. |CDS| printed the ROUTER build ID, but the "Welcome to NDDS" 
message, NDDS C, and NDDS Core Library build IDs weren't printed. 
This problem was new (a regression) in |CONNEXT| 6.0.

This problem has been resolved. The Core Library verbosity is now set 
before |CDS| starts, allowing the initialization to appear in the log. 
For example, running ``rticlouddiscoveryservice -verbosity 6``, as in 
previous releases, now yields the following:

.. code-block:: c 

   ...
   DDS_DomainParticipantFactory_initializeI:Welcome to NDDS
   NDDSCORE_BUILD_5.3.1.0_20180216T211030Z_RTI_REL
   NDDSC_BUILD_5.3.1.0_20180216T211030Z_RTI_REL
   ...

[RTI Issue ID CDS-51]


Transport element in XML did not remove default UDPv4 transport 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Even if you specified a transport other than udpv4 (for example, 
tcpv4_lan), |CDS| kept listening for announcements using the udpv4 
transport. The only way to ensure that the udpv4 transport wasn't 
used was to use the command-line arguments. This problem has been 
resolved.

[RTI Issue ID CDS-53]


Previous Releases 
-----------------

What's Fixed in 6.0.0
^^^^^^^^^^^^^^^^^^^^^

Transport configuration property XML inconsistent with documentation
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
The XML definition of the <property> tag under <transport> was inconsistent
with the documented definition, which indicates that the first and only
element must be the tag <value>. This problem has been resolved: the 
<property> tag now behaves as described in the documentation.

[RTI Issue ID CDS-37]

Domain Tag ignored for repeated announcements
'''''''''''''''''''''''''''''''''''''''''''''
|CDS| did not correctly apply the domain tag for announcements of already 
discovered participants. This caused the domain tag functionality to have 
no effect. This problem has been resolved.

[RTI Issue ID CDS-44]