You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new master branch of the RealSense ROS2 wrapper called ros2-master has been created and set as the default branch for the wrapper. The Readme and Contributing files have been updated to reflect the change.
ros2-master will be the stable branch and should be always compatible with the librealsense master branch and with all librealsense latest releases. ros2-master can be built from source, or installed by sudo apt install (debians are available in the ROS apt).
The ros2-development branch must be built from source code as no debians are available for it, like how there are no debians for the development branch of the librealsense SDK.
All daily development and new features will continue to be developed under ros2-development, which might require working with the librealsense development branch, especially when new APIs are being added in both sides.
When a new version of librealsense is released, ros2-master will be updated to be aligned with ros2-development.
The text was updated successfully, but these errors were encountered:
Hi everyone,
A new master branch of the RealSense ROS2 wrapper called ros2-master has been created and set as the default branch for the wrapper. The Readme and Contributing files have been updated to reflect the change.
ros2-master will be the stable branch and should be always compatible with the librealsense master branch and with all librealsense latest releases. ros2-master can be built from source, or installed by sudo apt install (debians are available in the ROS apt).
The ros2-development branch must be built from source code as no debians are available for it, like how there are no debians for the development branch of the librealsense SDK.
All daily development and new features will continue to be developed under ros2-development, which might require working with the librealsense development branch, especially when new APIs are being added in both sides.
When a new version of librealsense is released, ros2-master will be updated to be aligned with ros2-development.
The text was updated successfully, but these errors were encountered: