ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A

New Packages for ROS 2 Dashing Diademata 2021-02-04

Small but stalwart sync for ROS 2 Dashing. Thanks to everyone who contributed to this release and those it builds on!

Package Updates for dashing

Note that package counts include dbgsym packages which have been filtered out from the list below

Added Packages [7]:

  • ros-dashing-rc-reason-clients: 0.2.1-1
  • ros-dashing-rc-reason-msgs: 0.2.1-1
  • ros-dashing-turtlebot3-fake-node: 2.2.1-1

Updated Packages [15]:

  • ros-dashing-cartographer-ros: 1.0.9000-1 β†’ 1.0.9003-1
  • ros-dashing-cartographer-ros-msgs: 1.0.9000-1 β†’ 1.0.9003-1
  • ros-dashing-laser-proc: 1.0.1-1 β†’ 1.0.2-1
  • ros-dashing-lgsvl-bridge: 0.2.0-1 β†’ 0.3.0-1
  • ros-dashing-rclc: 0.1.4-1 β†’ 0.1.7-1
  • ros-dashing-rclc-examples: 0.1.4-1 β†’ 0.1.7-1
  • ros-dashing-rclc-lifecycle: 0.1.4-1 β†’ 0.1.7-1
  • ros-dashing-turtlebot3-gazebo: 2.0.1-1 β†’ 2.2.1-1
  • ros-dashing-turtlebot3-simulations: 2.0.1-1 β†’ 2.2.1-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Chad Rockey
  • Chris Lalancette
  • Felix Ruess
  • Jan Staschulat
  • Martins Mozeiko
  • Will Son
  • ruess

Because of the layout of the post, to me it always looks like the maintainers are the removed packages :smile:
Especially if there are no removed packages.

Maybe it’s just me. Maybe it’s easy to add

  • none

below the Removed Packages [0]: header.

1 Like

I added a horizontal rule, which is what I usually prefer for visual separation rather than adding items to what should be an empty list. If that seems reasonable we can consider a patch in reprepro-updater/ at refactor Β· ros-infrastructure/reprepro-updater Β· GitHub

Horizontal line will do!