Skip to content

What to do about ROS 2 support? #646

@sea-bass

Description

@sea-bass

I have recently implemented ROS 2 action support in rosbridge_suite in RobotWebTools/rosbridge_suite#886, and a working client in roslibjs in #645.

However, this leaves a few questions open regarding ROS 2 support for this library. Namely,

  • Right now, there is still a lot of functionality not ported to ROS 2 (with the exception of topics/services, basically)
  • There are no ROS 2 examples
  • CI is only running on melodic/noetic, but there are no jobs for e.g. humble/iron

So, what should the plan be going forward?

  • Keep the develop branch on ROS 1 and start tackling the CI/testing revamping on the ros2 branch?
  • Spinning up a new ros2libjs repo?
  • Other?

Metadata

Metadata

Assignees

No one assigned

    Labels

    v2Issues and PRs, which will be fixed in v2, as it is a breaking change

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions