Document that cross-distro communications are not guaranteed#5640
Merged
christophebedard merged 1 commit intorollingfrom May 20, 2025
Merged
Conversation
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
|
HTML artifacts: https://github.com/ros2/ros2_documentation/actions/runs/15126110217/artifacts/3156020876. To view the resulting site:
|
Comment on lines
+208
to
+215
|
|
||
| Cross-Distribution Communications | ||
| --------------------------------- | ||
|
|
||
| Nodes are not guaranteed to be able to communicate across distributions. | ||
| For example, a node built & running against Humble is not guaranteed to be able to communicate correctly with a node built & running against Iron. | ||
| It may or may not work, but it is not supported and should not be relied upon. | ||
| Note that :ref:`cross-vendor (single-distro) communications are also not guaranteed <different-middleware-vendors-cross-vendor-communication>`. |
Member
Author
There was a problem hiding this comment.
The exact language could be changed. I also intentionally didn't get into why it may or may not work and why it's not supported, but I'm open to mentioning something specific.
Member
Author
|
Alright, thanks for the review. Let's go with this now, and we can always change it later. |
mergify bot
pushed a commit
that referenced
this pull request
May 20, 2025
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com> (cherry picked from commit eed8fda)
mergify bot
pushed a commit
that referenced
this pull request
May 20, 2025
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com> (cherry picked from commit eed8fda)
mergify bot
pushed a commit
that referenced
this pull request
May 20, 2025
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com> (cherry picked from commit eed8fda)
This was referenced May 20, 2025
christophebedard
added a commit
that referenced
this pull request
May 20, 2025
christophebedard
added a commit
that referenced
this pull request
May 20, 2025
christophebedard
added a commit
that referenced
this pull request
May 20, 2025
|
This pull request has been mentioned on ROS Discourse. There might be relevant details there: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Relates to #3288. #4736 (which closed #3288) added a section about cross-
rmwvendor communications not being guaranteed. #3288 also mentioned cross-distro communications, but it was not documented.This new Discourse post is asking about cross-distro (in)compatibility: https://discourse.ros.org/t/incompatability-between-distributions/43747. We've talked about it not being guaranteed many times before, but I don't think it's mentioned anywhere in the docs (but I could be wrong). Since it's about multiple distros and not a specific distro, it's hard to find a place to document this, but I think the main distributions/releases page works well. I'm open to other suggestions, though.
Did you use Generative AI?
no
Additional Information