Can Ardent nodes talk to Bouncy nodes?
According to the release notes for Bouncy and observed behavior, it does not use partitions anymore for namespaces.
From https://github.com/ros2/ros2/wiki/Rel... :
The ROS topic names containing namespaces are mapped to DDS topics including their namespaces. DDS partitions are not being used anymore for this.
Is there any backwards compatibility?
My experiments with docker ardent-basic and bouncy-basic fail, but bouncy-basic containers can talk to each other.
Do you have a specific use case why you need to mix both releases? If there anything which works for you with the Ardent release but not for the Bouncy release? Otherwise you should be able to just move forward to Bouncy.
Bouncy does not work on 16.04 and we have robots on both 16.04 and 18.04. This is a problem because it is hard to switch between bouncy and ardent on our development computers. The robots on 16.04 require "certified" software (i.e. slow moving code with little to no maintenance personnel)
From the Bouncy release page, building Bouncy from source on 16.04 is supported, but binary packages aren't being provided.
@calvertdw can you provide more details about what bouncy nodes dont work for you in Xenial?
AFAIK all bouncy ROS 2 packages work on both platforms. The few exceptions are: cartographer and cv_bridge. A xenial build of the bouncy release is available at ...
... https://github.com/ros2/ros2/releases...
I missed that bouncy was supported on 16.04, so I did not have any nodes that weren't working. Thank you.