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
Copy file name to clipboardExpand all lines: source/The-ROS2-Project/Roadmap.rst
+10-27Lines changed: 10 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,39 +15,22 @@ This page describes planned work for ROS 2.
15
15
The set of planned features and development efforts should provide insight into the overall direction of ROS 2.
16
16
If you would like to see other features on the roadmap, please get in touch with us at [email protected].
17
17
18
-
Kilted Roadmap
19
-
--------------
18
+
Lyrical Luth
19
+
------------
20
20
21
-
Kilted Kaiju is the ROS 2 release expected in May 2025.
22
-
See the :doc:`release page <../Releases/Release-Kilted-Kaiju>` for a detailed timeline.
21
+
Lyrical Luth is the ROS 2 release expected in May 2026.
22
+
See the :doc:`release page <../Releases/Release-Lyrical-Luth>` for a detailed timeline.
23
23
24
-
The items in the roadmap below are the major features being worked on by the ROS 2 community.
24
+
Lyrical Roadmap
25
+
---------------
26
+
27
+
The features being worked on are tracked on the `GitHub Project Board <https://github.com/orgs/ros2/projects/70>`__.
28
+
The items in the roadmap are the major features being worked on by the ROS 2 community.
25
29
The "Size" is an estimated size of the task, where *Small* means person-days to complete, *Medium* means person-weeks to complete, and *Large* means person-months to complete.
26
30
27
-
If you are working on a feature for ROS 2 and would like to have it listed, please open a pull request to `ROS 2 Documentation <https://github.com/ros2/ros2_documentation>`__.
31
+
If you are working on a feature for ROS 2 and would like to have it listed, please open an issue on `ROS 2 Documentation <https://github.com/ros2/ros2_documentation>`__.
28
32
If you'd like to take on one of these tasks, please :doc:`get in touch with us <../Contact>`.
The ``rmw`` interface as defined by that package does not support passing arbitrary configuration data to the implementation or the underlying middleware.
459
-
To get around that and introduce some flexibility, some implementations use environment variables: ``RMW_FASTRTPS_*``, ``RMW_CONNEXT_*``, etc.
458
+
The ``rmw`` interface allows providing arbitrary implementation-specific configuration payloads for publishers and subscriptions through the type-erased ``rmw_specific_publisher_payload`` / ``rmw_specific_subscription_payload`` fields in ``rmw_publisher_options_t`` / ``rmw_subscription_options_t``.
459
+
This is set by users through ``RMWImplementationSpecificPublisherPayload`` / ``RMWImplementationSpecificSubscriptionPayload`` in ``rclcpp``, for example.
460
+
This is an advanced, non-portable feature that is not currently used by any (tier 1) implementations.
461
+
462
+
For a bit more flexibility, some implementations use environment variables: ``RMW_FASTRTPS_*``, ``RMW_CONNEXT_*``, etc.
460
463
The underlying middleware may also be configurable through environment variables: ``FASTDDS_*``, ``ZENOH_*``, ``CYCLONEDDS_*``, ``EMAIL_*``, etc.
461
464
For example, the ``CYCLONEDDS_URI``, ``FASTDDS_DEFAULT_PROFILES_FILE``, and ``ZENOH_SESSION_CONFIG_URI`` environment variables can be used to provide a path to a full configuration file if the relevant middleware is used.
0 commit comments