You're reading the documentation for a version of ROS 2 that has reached its EOL (end-of-life), and is no longer officially supported. If you want up-to-date information, please have a look at Iron.
ROS 2 Humble Hawksbill (codename ‘humble’; May, 2022)
Humble Hawksbill is the eighth release of ROS 2. What follows is highlights of the important changes and features in Humble Hawksbill since the last release.
Supported Platforms
Humble Hawksbill is primarily supported on the following platforms:
Tier 1 platforms:
TBD
Tier 2 platforms:
TBD
Tier 3 platforms:
TBD
For more information about RMW implementations, compiler / interpreter versions, and system dependency versions see REP 2000.
Installation
To come.
New features in this ROS 2 release
To come.
Changes since the Galactic release
ros2cli
ros2 topic pub will wait for one matching subscription when using --times/--once/-1
When using --times/--once/-1 flags, ros2 topic pub will wait for one matching subscription to be found before starting to publish.
This avoids the issue of the ros2cli node starting to publish before discovering a matching subscription, which results in some of the first messages being lost.
This is particularly unexpected when using a reliable qos profile.
The number of matching subscriptions to wait before starting publishing can be configured with the -w/--wait-matching-subscriptions flags, e.g.:
`
ros2 topic pub -1 -w 3 /chatter std_msgs/msg/String "{data: 'foo'}"
`
to wait for three matching subscriptions before starting to publish.
-w can also be used independently of --times/--once/-1 but it only defaults to one when combined with them, otherwise the -w default is zero.
See https://github.com/ros2/ros2cli/pull/642 for more details.
ros2 param dump default output changed
It prints to stdout by default:
ros2 param dump /my_node_name
--output-diroption for dump command was deprecated.To dump parameters to a file, run:
ros2 param dump /my_node_name > my_node_name.yaml
Known Issues
To come.
Release Timeline
To come.