Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: Transforming Rahal Robot for ROS 2 Humble with Gazebo Sim

Hello ROS community!

I’ve been working on evolving the Rahal Robot to fully utilize the power of ROS 2 Humble and Gazebo Sim, and I’m thrilled to share the progress with you all! This project has been a rewarding experience, bringing new life to a ROS 1 classic and adapting it to modern robotics needs.

What’s New?

  • Transitioned the Rahal Robot to ROS 2 with a refined SDF model, ensuring full compatibility with Gazebo Sim.
  • Enhanced perception by adding LiDAR and a camera, enabling improved mapping and object detection.
  • Integrated slam_toolbox for autonomous mapping and better localization capabilities.
  • Added a personal touch by incorporating the Arab Meet logo into the Gazebo Sim model.

Why This Matters

The migration to ROS 2 Humble not only modernizes the Rahal Robot but also sets the stage for future innovations. With better tools, updated simulation environments, and enhanced navigation possibilities, this robot is ready to tackle new challenges.

The original ROS 1 version that inspired this journey can be found here:
Original Rahal Robot Repository

For ROS 2 enthusiasts, you can explore my upgraded version, which includes updated code, documentation, and simulation files, here:
My Rahal Robot Repository

What’s Next?

I’m excited to explore Nav2 to push the navigation capabilities even further. This project is just the beginning, and I can’t wait to see where it leads.

Your feedback, suggestions, and collaborations are always welcome. Let’s continue innovating together in this amazing ROS community!

ros2 #GazeboSim #slam_toolbox #RobotNavigation nav2 #OpenRobotic

raalslamtoolbox

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/transforming-rahal-robot-for-ros-2-humble-with-gazebo-sim/41520

ROS Discourse General: Rust implementation of RMW Zenoh for ROS2 Humble

Hey there! I’m using ROS2 Humble at work, and I’ve been studying ROS2.
Since Zenoh wasn’t supported on Humble until recently, I figured I’d learn Rust and give building a Zenoh RMW in Rust a shot.

I kicked off the project last month, but the official Humble version released last week, so my work might already be outdated (haha).
If you try it out, I’d love to hear what you think.

I’m also looking to contribute to the official rmw_zenoh moving forward. Thanks!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/rust-implementation-of-rmw-zenoh-for-ros2-humble/41510

ROS Discourse General: ROS News for the Week of January 6th, 2025

ROS News for the Week of January 6th, 2025

ROSBTBJan25 (1)

Our next ROS By-The-Bay will be on 2025-01-30 @tomoyafujita and @Yadunund will be on hand to talk about the new Zenoh RMW and rcl_logging_syslog.


image

CES was this week and there were quite a few new developments in the world of robotics. The image above is of a water quality monitoring robot from a new company called Beatbot. My personal favorite was this new prototype IR touch sensor from Thinker robotics. Our friends at the Indy Autonomous Challenge were competing at the Las Vegas Motor Speedway all week. I’ve collected a bunch of CES related articles in the news section.


image

Our friends over at PicNick have put together a fantastic resource that lists every robot arm that is ROS compatible along with detailed information about the ROS package that supports the hardware. I suggest book marking this webpage!


image

Check out this amazing plugin that allows you to import your Nav2 maps directly into Gazebo. This is a super tool for anyone working on Nav2 development,


image

@audrow has released a new podcast episode. In this episode he interviews a bunch of interesting attendees from ROSCon 2024 in Denmark.


image

A research team over at University of Cardiff have released a Gazebo simulation for the popular Stretch Robot by Hello Robot. The sim works with ROS 2 Humble and modern Gazebo (Harmonic).


Events

News

ROS

Got a Minute? :mantelpiece_clock:

I am looking for two people (C++ / Python) to help write a very simple addition for the documentation of ROS 2 parameters.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-january-6th-2025/41487

ROS Discourse General: Next Client Library WG Meeting: Friday 10 January 2025 8AM PT

Hi,
The client library WG meeting is back after the new year’s break.

The next meeting of the Client Library Working Group will be this Friday, 10th January 2025 at 8 AM Pacific Time.

The focus of the discussion will be some critical rclcpp bugs around the waitset and executor. See agenda for details.

Everyone is welcome to join to contribute to this topics or bring up new ones

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/next-client-library-wg-meeting-friday-10-january-2025-8am-pt/41458

ROS Discourse General: How many hardware brands have good ROS 2 Drivers? Announcing a new resource for the ROS Community

PickNik is proud to announce the launch of the ROS 2 Hardware Drivers partners page, a new online resource showcasing robot hardware, particularly robotic arms, that are compatible with the ROS 2. This initiative is a direct result of PickNik’s long term dedication to ROS, open source, and creating open source ROS drivers for various brands of hardware. This work was undertaken by PickNik in response to needs raised at a meeting held at ROSCon 2024 by the OSRF, PickNik, ROS Industrial, and other key contributors.

The ROS 2 Hardware Drivers page is designed to serve as a useful resource for developers, integrators, and researchers, enabling them to identify compatible hardware for their ROS 2-based projects efficiently. It also acts as a barometer for the widespread adoption of ROS 2 middleware worldwide. The page lists all robots with known ROS 2 compatibility and is continually updated. If you know of ROS 2-compatible robots or components not yet featured, let us know—we’re happy to add them. PickNik also offers ROS 2 driver development services to further support the community.

Terminology

To guide users, the page incorporates a ROS 2 Driver quality score ranking methodology and introduces some terminology to better classify types of drivers:

  • Great: High-bandwidth streaming, typically > 500 Hz
    • The most complex drivers to write and the most powerful: these drivers enable visual servoing, dextrous manipulation on top of a mobile base, and sensitive force compliance (if you have a force torque sensor).
  • Average: Low-bandwidth trajectory, typically < 25 Hz
    • These allow you to avoid static obstacles you have sensed at planning time.
  • Poor: Low-bandwidth single-point, typically < 25 Hz
    • These drivers are difficult to use in advanced applications. Avoiding collisions is difficult because you cannot stream commands around the obstacles or provide a pre-planned trajectory around it.

We’re particularly excited to include details about compatibility with MoveIt Pro, our advanced solution for ML, perception, motion planning, and control. The “Compatible with MoveIt Pro” designation comes in two tiers. Gold Integration signifies hardware that PickNik has rigorously tested, complete with a working ROS 2 driver and MoveIt Pro configuration we endorse. Basic Integration indicates successful integration by a third-party company, though it has not undergone validation by PickNik.

We believe the robotics industry is so much stronger thanks to interoperability with ROS!

10 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/how-many-hardware-brands-have-good-ros-2-drivers-announcing-a-new-resource-for-the-ros-community/41446

ROS Discourse General: CES 2025 - Isaac ROS 3.2 and platform updates

NVIDIAIsaac

From CES 2025, discover key updates to the NVIDIA Isaac platform that streamline your end-to-end development of robotics systems from simulation to real-world deployment.
NVIDIA
Read the NVIDIA Isaac technical blog to learn more about the updates to the following:

  • Isaac ROS 3.2
    • Isaac Manipulator
    • Isaac Perceptor
  • Isaac Sim
  • Isaac Lab

Read here.

If you didn’t get a chance to watch Jensen’s keynote discussions at CES 2025. Watch it again here.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ces-2025-isaac-ros-3-2-and-platform-updates/41444

ROS Discourse General: Cloud Robotics WG Meeting 2025-01-13

Please come and join us for this coming meeting at 1700-1800 UTC on Monday 13th January 2025, where we will discuss the latest in Cloud Robotics news. The session will be more of an informal chat.

Last meeting, we hosted a talk from Tomoya Fujita on Robotics Platforms empowered by Cloud-Native Technologies. If you’re interested to see the talk, we have published it on YouTube.

If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on YouTube with our other meeting recordings too!

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.

Hopefully we will see you there!

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/cloud-robotics-wg-meeting-2025-01-13/41441

ROS Discourse General: Mesh2gazebo: Building a simulator environment using mesh data of 3D Scan Application

I proposed tool(mesh2gazebo) to build simulator environment using mesh data of 3D Scan Application. If you are interested in this tool, please read https://www.docswell.com/s/dandelion1124/5DNMRW-2025-01-07-150727.

3 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/mesh2gazebo-building-a-simulator-environment-using-mesh-data-of-3d-scan-application/41435

ROS Discourse General: TF tree in a multi-robot setup in ROS2

Hello everyone,

with our recent switch to ROS2, we want to make our setup ready for multi-robot operation. Unfortunately, there does not seem to be an established standard (or better yet, a REP) for this and I could only find little discussion on the topic.

Therefore, we would like the hear about everyone’s experiences and best-practices for a multi-robot setup in ROS2.

The main problem seems to be how to organize the tf tree and frame names. Currently, we are considering these three options:

Option A: tf/frame prefix

The robot_state_publisher has the option to prepend a frame_prefix (previously tf_prefix) which would make each frame name globally unique.

Pro:

  • Globally unique frame name

Contra:

  • Support was temporarily dropped during transition from melodic to noetic. Therefore, barely any node supports this anymore.
  • frame names do not match URDF link names (so nodes that use tf and URDF need to be aware of the prefix)

Option B: Multiple tf trees

Each robot has its own tf tree (/robot_name/tf). Nodes operate as usual in their own namespace. As far as I know, this is the option nav2 is using.

Additionally, tf transforms can be republished to a global tf topic with frame prefix.

Pro:

  • All nodes should work as usual in the robot-specific namespace

Contra:

  • Nodes that reason over multiple robots (global detection fusion, inter-robot collision avoidance …) need special handling
  • Sensor messages do not have a globally-unique frame id

Option C: Prefix URDF links

A robot-specific prefix can be inserted directly in the URDF, making the robot’s frame names globally unique.

Pro:

  • Should be supported by all nodes
  • Globally unique frame_id in sensor messages
  • TF frame names match URDF link names

Contra:

  • The robot name needs to be passed to pretty much every launch file as an argument
  • The MoveIt SRDF file needs to be a xacro to prepend the frame prefix to link names

What do you think? Does any one of you have experience with any of these options or do you even use an entirely different approach? I would be grateful for any experiences you could share.

Best regards,
Martin

12 posts - 6 participants

Read full topic

[WWW] https://discourse.ros.org/t/tf-tree-in-a-multi-robot-setup-in-ros2/41426

ROS Discourse General: Visualize your custom messages on RViz!

Happy new year everyone!!! :smile:

I’d like to share the release of a fun project I had been working on: ROS 2 CMV! - a custom message visualizer for RViz. With this package, you can generate rviz plugins for your custom messages!! The link to the repository is https://github.com/suchetanrs/ros2_cmv
This can be done using a GUI or directly in your CMakeLists by adding the following line just after the creation of your message:

generate_rviz_plugin("msg/Sample.msg")

Here are some plugins I was able to generate and play around with.

  1. A 2D occupancy map + markers showing the heights of obstacles + robot path with the evolution of the covariance over time.
  2. Similar to the previous one, but a live demonstration of a robot moving in a corridor.
  3. A snapshot of two robots with the paths that they will take, the laser-scan and a couple of obstacles (I should have done better here :p)
    All of this is visualized in a single message type!

If you like my work, please do leave a :star: on the repository. It will mean the world to me!

1 - map_walls_posees_cov
2 - robot_corridor
3 - two_robots

6 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/visualize-your-custom-messages-on-rviz/41409

ROS Discourse General: RobotCAD 5 - Sense released! (sensors and ROS2 Jazzy)

RobotCAD 5 demo

Changes

https://github.com/drfenixion/freecad.robotcad

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/robotcad-5-sense-released-sensors-and-ros2-jazzy/41402

ROS Discourse General: 🎉 rmw_zenoh binaries for Rolling, Jazzy and Humble

Hi everyone,

New year, new RMW!

We’ve released rmw_zenoh binaries for ROS 2 Rolling, Jazzy and Humble on respective Ubuntu (amd64, arm64) and RHEL (amd64) platforms.

Install rmw_zenoh binaries

The package can be installed with the command sudo apt install ros-<DISTRO>-rmw-zenoh-cpp. (Replace <DISTRO> with either rolling, jazzy or humble).

The binaries will be available after the next package sync for the respective distributions but in the meanwhile, you can get the pre-release binaries from the testing repository by following this guide.

Note: We strongly recommend using rmw_zenoh on Jazzy and Rolling as these versions are feature complete and have been extensively tested. We have not tested the Humble version ourselves and are expecting the community to help maintain it.

Once installed, you’ll be able to switch to rmw_zenoh by setting the RMW_IMPLEMENTATION environment variable to rmw_zenoh_cpp as seen below.

export RMW_IMPLEMENTATION=rmw_zenoh_cpp

Don’t forget to run the Zenoh router in a separate terminal prior!

ros2 run rmw_zenoh_cpp rmw_zenohd

For more information on usage, configuration, and known issues please see the README. An overview of rmw_zenoh along with its capabilities was presented at ROSCon 2024 Odense and the recording is available here.

Finally, a reminder that rmw_zenoh is not yet an official Tier-1 middleware in ROS 2 but our goal is to get there for the Kilted release in May. We hope these binaries will make it easier for the community to switch to rmw_zenoh and provide feedback!

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/rmw-zenoh-binaries-for-rolling-jazzy-and-humble/41395

ROS Discourse General: ROS News for the Week of December 30th, 2024 / 2025 :TADA:

ROS News for the Week of December 30th, 2024 / 2025 :tada:


image

@rkent has been working diligently for months on a whole host of pull requests to improve ROS Index and the ROS 2 documentation process. He is currently seeking feedback on experimental tools in ROS Index. Please take a moment to take a look at his work and offer your feedback!


ros2-navigation-tuning-guide-parameters-3-1024x529

Earlier in December Automatic Addison published a lovely tutorial on tuning Nav2.


68747470733a2f2f72742d6e65742e6769746875622e696f2f696d616765732f7261737062657272792d70692d6d6f7573652f5261737062657272792d50692d4d6f7573652e706e67

This week our colleagues at RT released a Jazzy version of their RaspiMouse robot. If you are looking for a smaller form factor educational robot it is worth checking out!


My Robot Bird Flies Like A REAL ONE

Aditya Nair, a graduate student at Northwestern, has a fantastic blog post about data-driven control for agile flight in a confined space. Aditya used a commercial robot bird toy, an Opti-track motion capture system, ROS 2 Humble, and an Arduino, to make it possible to fly the drone safely indoors. video


image

Happy New Year! :turtle: :tada: I have some bonus turtle content for this week. Here is a happy family of Florida Red Bellied Cooters I saw in the Everglades this week.

Events

News

ROS

Got a Minute?

:clap: WE :clap: NEED :clap: MORE :clap: PR :clap: REVIEWERS :clap:

PR reviews are a great way to dip your toes into open source development!

Don’t let imposter syndrome stop you. If you are reading this you are probably qualified to review a ROS PR!

Below is a list of seven easy ROS 2 pull requests that could really use your review!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-december-30th-2024-2025/41389

ROS Discourse General: Package discovery - experimental tools in rosindex, and request for experiences

I’ve been working on upgrades to rosindex recently, which I view as the primary tool in the ROS ecosystem for package discovery. I’d like to solicit comments here on some proposed features to help package discovery, as well as get any general comments on what would help package discovery in ROS.

My development rosindex build, which is many commits ahead of the official version, has in addition to major changes in package search, two new fields aimed at package discovery: relative download counts for each package, and whether the package is “core” (which I define as required by desktop_full). You can see the package search page here. You can sort packages by download count by clicking on the down arrow ↓. Whether a package is core or not is shown by the target ⊙. You can exclude core packages by entering core:false in the search bar.

Any comments on whether this is useful, or suggestions on how it might be improved? I included the “core” column and filter because I tend to find that download counts are normally dominated by core packages, which I don’t need to see if I am trying to find an interesting undiscovered package.

I’d also like to hear any general comments on package discovery, such as existing useful tools for this, or what would make it easier.

22 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/package-discovery-experimental-tools-in-rosindex-and-request-for-experiences/41374

ROS Discourse General: I just joined a autonomous driving startup. May I have some guidance here?

Basically, the company is doing autonomous driving R&D. They provide ultra-skateboard chassis powered by Autoware/ROS2 for autonomous driving studies and have their own self-driving Robobus.

I am in the business team, and I wonder is this a good career start point? (Do you buy chassises for your own projects? What kind of function are you looking for for your autonomous driving researches? What’s your suggestions for me to start with Autoware? :face_holding_back_tears:

5 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/i-just-joined-a-autonomous-driving-startup-may-i-have-some-guidance-here/41369

ROS Discourse General: Ros2cd - a complete roscd replacement in ros2

Hello everyone,

we recently moved to ros2 but I quickly noticed the lack of an equivalent for the old roscd. For me, this was an essential functionality to navigate workspaces efficiently. I know there is colcon_cd but it is very limited in functionality and basically only works in the current workspace.

As I could not find any alternative, I just wrote my own:

Simply source the bash file and off you go. The provided script replicates the behavior of the old roscd command in ros2 (and shares the name because of muscle memory). The current working directory is changed to the same one where ros2 launch would execute a launch file from. If a sym-link install is found, it goes to the source directory instead.

Best regards,
Martin

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros2cd-a-complete-roscd-replacement-in-ros2/41368

ROS Discourse General: New packages and patch release 3 for Jazzy Jalisco 2024-12-23

After regressions were fixed, we’re happy to announce the latest Jazzy Jalisco patch release 3.

After the sync 103 new packages and 744 updates are now available on Ubuntu Noble on amd64 for Jazzy Jalisco.

This sync was tagged as jazzy/2024-12-23 .

:jazzy: :jazzy: :jazzy:

Package Updates for jazzy

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

Added Packages [103]:

  • ros-jazzy-axis-camera: 3.0.1-1
  • ros-jazzy-axis-description: 3.0.1-1
  • ros-jazzy-axis-msgs: 3.0.1-1
  • ros-jazzy-boost-sml-vendor: 1.1.11-1
  • ros-jazzy-camera-info-manager-py: 5.1.5-1
  • ros-jazzy-camera-ros: 0.2.1-1
  • ros-jazzy-canopen: 0.3.0-1
  • ros-jazzy-canopen-402-driver: 0.3.0-1
  • ros-jazzy-canopen-base-driver: 0.3.0-1
  • ros-jazzy-canopen-core: 0.3.0-1
  • ros-jazzy-canopen-master-driver: 0.3.0-1
  • ros-jazzy-canopen-proxy-driver: 0.3.0-1
  • ros-jazzy-canopen-ros2-control: 0.3.0-1
  • ros-jazzy-canopen-ros2-controllers: 0.3.0-1
  • ros-jazzy-canopen-tests: 0.3.0-1
  • ros-jazzy-clearpath-motor-msgs: 1.0.1-1
  • ros-jazzy-clearpath-msgs: 1.0.1-1
  • ros-jazzy-clearpath-platform-msgs: 1.0.1-1
  • ros-jazzy-clearpath-ros2-socketcan-interface: 2.0.0-1
  • ros-jazzy-clips-vendor: 6.4.3-2
  • ros-jazzy-dual-laser-merger: 0.3.1-1
  • ros-jazzy-eiquadprog: 1.2.9-1
  • ros-jazzy-etsi-its-mapem-ts-coding: 3.0.0-1
  • ros-jazzy-etsi-its-mapem-ts-conversion: 3.0.0-1
  • ros-jazzy-etsi-its-mapem-ts-msgs: 3.0.0-1
  • ros-jazzy-etsi-its-spatem-ts-coding: 3.0.0-1
  • ros-jazzy-etsi-its-spatem-ts-conversion: 3.0.0-1
  • ros-jazzy-etsi-its-spatem-ts-msgs: 3.0.0-1
  • ros-jazzy-gpio-controllers: 4.18.0-1
  • ros-jazzy-marker-msgs: 0.0.8-1
  • ros-jazzy-mecanum-drive-controller: 4.18.0-1
  • ros-jazzy-moveit-ros-trajectory-cache: 2.12.1-1
  • ros-jazzy-neo-nav2-bringup: 1.3.0-1
  • ros-jazzy-raspimouse: 2.0.0-1
  • ros-jazzy-raspimouse-fake: 3.0.1-1
  • ros-jazzy-raspimouse-gazebo: 3.0.1-1
  • ros-jazzy-raspimouse-msgs: 2.0.0-1
  • ros-jazzy-raspimouse-navigation: 3.0.0-1
  • ros-jazzy-raspimouse-ros2-examples: 3.0.0-1
  • ros-jazzy-raspimouse-sim: 3.0.1-1
  • ros-jazzy-raspimouse-slam: 3.0.0-1
  • ros-jazzy-raspimouse-slam-navigation: 3.0.0-1
  • ros-jazzy-rosbag2-to-video: 1.0.1-1
  • ros-jazzy-tuw-airskin-msgs: 0.2.4-1
  • ros-jazzy-tuw-geo-msgs: 0.2.4-1
  • ros-jazzy-tuw-geometry-msgs: 0.2.4-1
  • ros-jazzy-tuw-graph-msgs: 0.2.4-1
  • ros-jazzy-tuw-msgs: 0.2.4-1
  • ros-jazzy-tuw-multi-robot-msgs: 0.2.4-1
  • ros-jazzy-tuw-nav-msgs: 0.2.4-1
  • ros-jazzy-tuw-object-map-msgs: 0.2.4-1
  • ros-jazzy-tuw-object-msgs: 0.2.4-1
  • ros-jazzy-tuw-std-msgs: 0.2.4-1
  • ros-jazzy-ur-simulation-gz: 2.1.0-2
  • ros-jazzy-wireless-msgs: 1.1.2-1
  • ros-jazzy-wireless-watcher: 1.1.2-1
  • ros-jazzy-yaets: 0.0.2-1
  • ros-jazzy-yasmin: 3.0.3-1
  • ros-jazzy-yasmin-demos: 3.0.3-1
  • ros-jazzy-yasmin-msgs: 3.0.3-1
  • ros-jazzy-yasmin-ros: 3.0.3-1
  • ros-jazzy-yasmin-viewer: 3.0.3-1

Updated Packages [744]:

  • ros-jazzy-ackermann-steering-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-admittance-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-ament-cmake: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-auto: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-core: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-definitions: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-dependencies: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-include-directories: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-interfaces: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-libraries: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-link-flags: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-export-targets: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-gen-version-h: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-gmock: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-google-benchmark: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-gtest: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-include-directories: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-libraries: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-pytest: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-python: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-target-dependencies: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-test: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-vendor-package: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-ament-cmake-version: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-autoware-common-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-control-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1
  • ros-jazzy-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1
  • ros-jazzy-autoware-localization-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-map-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-perception-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-planning-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-sensing-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-system-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-v2x-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-autoware-vehicle-msgs: 1.2.0-1 → 1.3.0-1
  • ros-jazzy-bicycle-steering-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-camera-aravis2: 1.0.0-1 → 1.1.0-1
  • ros-jazzy-camera-aravis2-msgs: 1.0.0-1 → 1.1.0-1
  • ros-jazzy-camera-calibration: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-camera-calibration-parsers: 5.1.4-1 → 5.1.5-1
  • ros-jazzy-camera-info-manager: 5.1.4-1 → 5.1.5-1
  • ros-jazzy-canopen-fake-slaves: 0.2.9-2 → 0.3.0-1
  • ros-jazzy-canopen-interfaces: 0.2.9-2 → 0.3.0-1
  • ros-jazzy-canopen-utils: 0.2.9-2 → 0.3.0-1
  • ros-jazzy-chomp-motion-planner: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-compressed-depth-image-transport: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-compressed-image-transport: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-control-toolbox: 3.3.0-1 → 3.4.0-1
  • ros-jazzy-controller-interface: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-controller-manager: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-controller-manager-msgs: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-costmap-queue: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-dataspeed-can: 2.0.4-1 → 2.0.5-1
  • ros-jazzy-dataspeed-can-msg-filters: 2.0.4-1 → 2.0.5-1
  • ros-jazzy-dataspeed-can-msgs: 2.0.4-1 → 2.0.5-1
  • ros-jazzy-dataspeed-can-tools: 2.0.4-1 → 2.0.5-1
  • ros-jazzy-dataspeed-can-usb: 2.0.4-1 → 2.0.5-1
  • ros-jazzy-depth-image-proc: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-diff-drive-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-ds-dbw: 2.2.3-1 → 2.3.1-1
  • ros-jazzy-ds-dbw-can: 2.2.3-1 → 2.3.1-1
  • ros-jazzy-ds-dbw-joystick-demo: 2.2.3-1 → 2.3.1-1
  • ros-jazzy-ds-dbw-msgs: 2.2.3-1 → 2.3.1-1
  • ros-jazzy-dual-arm-panda-moveit-config: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-dwb-core: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-dwb-critics: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-dwb-msgs: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-dwb-plugins: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-effort-controllers: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-ess-imu-driver2: 2.0.2-1 → 2.0.3-1
  • ros-jazzy-etsi-its-cam-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cam-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cam-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cam-ts-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cam-ts-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cam-ts-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cpm-ts-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cpm-ts-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-cpm-ts-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-denm-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-denm-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-denm-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-messages: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-msgs-utils: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-primitives-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-rviz-plugins: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-vam-ts-coding: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-vam-ts-conversion: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-etsi-its-vam-ts-msgs: 2.3.0-1 → 3.0.0-1
  • ros-jazzy-examples-tf2-py: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-fastcdr: 2.2.4-1 → 2.2.5-1
  • ros-jazzy-fastrtps: 2.14.3-1 → 2.14.4-1
  • ros-jazzy-fastrtps-cmake-module: 3.6.0-2 → 3.6.1-1
  • ros-jazzy-flir-camera-description: 2.0.20-1 → 3.0.0-1
  • ros-jazzy-flir-camera-msgs: 2.0.20-1 → 3.0.0-1
  • ros-jazzy-force-torque-sensor-broadcaster: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-forward-command-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-foxglove-bridge: 0.8.0-1 → 0.8.2-1
  • ros-jazzy-game-controller-spl: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-game-controller-spl-interfaces: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-gc-spl: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-gc-spl-2022: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-gc-spl-interfaces: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-geometric-shapes: 2.2.1-1 → 2.3.1-1
  • ros-jazzy-geometry2: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-gripper-controllers: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-gz-dartsim-vendor: 0.0.2-1 → 0.0.3-1
  • ros-jazzy-gz-ros2-control: 1.2.8-1 → 1.2.9-1
  • ros-jazzy-gz-ros2-control-demos: 1.2.8-1 → 1.2.9-1
  • ros-jazzy-hardware-interface: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-hardware-interface-testing: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-iceoryx-binding-c: 2.0.5-6 → 2.0.6-1
  • ros-jazzy-iceoryx-hoofs: 2.0.5-6 → 2.0.6-1
  • ros-jazzy-iceoryx-introspection: 2.0.5-6 → 2.0.6-1
  • ros-jazzy-iceoryx-posh: 2.0.5-6 → 2.0.6-1
  • ros-jazzy-image-common: 5.1.4-1 → 5.1.5-1
  • ros-jazzy-image-pipeline: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-image-proc: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-image-publisher: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-image-rotate: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-image-transport: 5.1.4-1 → 5.1.5-1
  • ros-jazzy-image-transport-plugins: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-image-view: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-imu-sensor-broadcaster: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-interactive-marker-twist-server: 2.1.0-3 → 2.1.1-1
  • ros-jazzy-joint-limits: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-joint-state-broadcaster: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-joint-trajectory-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-kitti-metrics-eval: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-launch: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-launch-pytest: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-launch-ros: 0.26.5-2 → 0.26.6-1
  • ros-jazzy-launch-testing: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-launch-testing-ament-cmake: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-launch-testing-ros: 0.26.5-2 → 0.26.6-1
  • ros-jazzy-launch-xml: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-launch-yaml: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-lely-core-libraries: 0.2.9-2 → 0.3.0-1
  • ros-jazzy-liblz4-vendor: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-libstatistics-collector: 1.7.3-1 → 1.7.4-1
  • ros-jazzy-lttngpy: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-mapviz: 2.4.3-1 → 2.4.4-1
  • ros-jazzy-mapviz-interfaces: 2.4.3-1 → 2.4.4-1
  • ros-jazzy-mapviz-plugins: 2.4.3-1 → 2.4.4-1
  • ros-jazzy-mcap-vendor: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-message-filters: 4.11.2-1 → 4.11.3-1
  • ros-jazzy-mola: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-bridge-ros2: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-demos: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-imu-preintegration: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-euroc-dataset: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-kitti-dataset: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-kitti360-dataset: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-mulran-dataset: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-paris-luco-dataset: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-rawlog: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-input-rosbag2: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-kernel: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-launcher: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-lidar-odometry: 0.3.3-1 → 0.4.0-1
  • ros-jazzy-mola-metric-maps: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-msgs: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-navstate-fg: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-navstate-fuse: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-pose-list: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-relocalization: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-traj-tools: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-viz: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-mola-yaml: 1.2.1-1 → 1.4.0-1
  • ros-jazzy-moveit: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-common: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-configs-utils: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-core: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-hybrid-planning: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-kinematics: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-msgs: 2.5.0-1 → 2.6.0-1
  • ros-jazzy-moveit-planners: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-planners-chomp: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-planners-ompl: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-planners-stomp: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-plugins: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-py: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-resources: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-fanuc-description: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-fanuc-moveit-config: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-panda-description: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-panda-moveit-config: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-pr2-description: 3.0.0-3 → 3.1.0-1
  • ros-jazzy-moveit-resources-prbt-ikfast-manipulator-plugin: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-resources-prbt-moveit-config: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-resources-prbt-pg70-support: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-resources-prbt-support: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-benchmarks: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-control-interface: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-move-group: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-occupancy-map-monitor: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-perception: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-planning: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-planning-interface: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-robot-interaction: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-tests: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-visualization: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-ros-warehouse: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-runtime: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-servo: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-app-plugins: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-assistant: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-controllers: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-core-plugins: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-framework: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-setup-srdf-plugins: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-simple-controller-manager: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-moveit-visual-tools: 4.1.0-4 → 4.1.1-1
  • ros-jazzy-mp2p-icp: 1.6.3-1 → 1.6.4-1
  • ros-jazzy-mrpt-apps: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libapps: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libbase: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libgui: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libhwdrivers: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libmaps: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libmath: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libnav: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libobs: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libopengl: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libposes: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libros-bridge: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libslam: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-mrpt-libtclap: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-multires-image: 2.4.3-1 → 2.4.4-1
  • ros-jazzy-mvsim: 0.11.1-1 → 0.12.0-1
  • ros-jazzy-nav-2d-msgs: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav-2d-utils: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-amcl: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-behavior-tree: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-behaviors: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-bringup: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-bt-navigator: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-collision-monitor: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-common: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-constrained-smoother: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-core: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-costmap-2d: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-dwb-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-graceful-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-lifecycle-manager: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-loopback-sim: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-map-server: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-mppi-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-msgs: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-navfn-planner: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-planner: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-rotation-shim-controller: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-rviz-plugins: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-simple-commander: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-smac-planner: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-smoother: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-system-tests: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-theta-star-planner: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-util: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-velocity-smoother: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-voxel-grid: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-nav2-waypoint-follower: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-navigation2: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-ntrip-client: 1.3.0-3 → 1.4.0-1
  • ros-jazzy-odom-to-tf-ros2: 1.0.3-2 → 1.0.4-1
  • ros-jazzy-opennav-docking: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-opennav-docking-bt: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-opennav-docking-core: 1.3.3-1 → 1.3.4-1
  • ros-jazzy-openvdb-vendor: 2.5.3-1 → 2.5.4-1
  • ros-jazzy-osrf-pycommon: 2.1.4-3 → 2.1.5-1
  • ros-jazzy-pal-statistics: 2.2.4-1 → 2.6.0-1
  • ros-jazzy-pal-statistics-msgs: 2.2.4-1 → 2.6.0-1
  • ros-jazzy-parallel-gripper-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-pick-ik: 1.1.0-4 → 1.1.1-1
  • ros-jazzy-pid-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-pilz-industrial-motion-planner: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-pilz-industrial-motion-planner-testutils: 2.10.0-1 → 2.12.1-1
  • ros-jazzy-plansys2-core: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-domain-expert: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-executor: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-lifecycle-manager: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-msgs: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-pddl-parser: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-planner: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-popf-plan-solver: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-problem-expert: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-support-py: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-plansys2-tools: 2.0.14-1 → 2.0.15-1
  • ros-jazzy-point-cloud-transport: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-point-cloud-transport-py: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-pose-broadcaster: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-position-controllers: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-python-mrpt: 2.14.5-1 → 2.14.7-1
  • ros-jazzy-qt-dotgraph: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-qt-gui: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-qt-gui-app: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-qt-gui-core: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-qt-gui-cpp: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-qt-gui-py-common: 2.7.4-2 → 2.7.5-1
  • ros-jazzy-range-sensor-broadcaster: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-rc-reason-clients: 0.3.1-3 → 0.4.0-2
  • ros-jazzy-rc-reason-msgs: 0.3.1-3 → 0.4.0-2
  • ros-jazzy-rcgcd-spl-14: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-rcgcd-spl-14-conversion: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-rcgcrd-spl-4: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-rcgcrd-spl-4-conversion: 4.0.1-1 → 4.1.0-1
  • ros-jazzy-rcl-logging-interface: 3.1.0-2 → 3.1.1-1
  • ros-jazzy-rcl-logging-noop: 3.1.0-2 → 3.1.1-1
  • ros-jazzy-rcl-logging-spdlog: 3.1.0-2 → 3.1.1-1
  • ros-jazzy-rclcpp: 28.1.5-1 → 28.1.6-1
  • ros-jazzy-rclcpp-action: 28.1.5-1 → 28.1.6-1
  • ros-jazzy-rclcpp-components: 28.1.5-1 → 28.1.6-1
  • ros-jazzy-rclcpp-lifecycle: 28.1.5-1 → 28.1.6-1
  • ros-jazzy-rclpy: 7.1.2-1 → 7.1.3-1
  • ros-jazzy-rcpputils: 2.11.0-2 → 2.11.1-1
  • ros-jazzy-realtime-tools: 2.8.1-1 → 3.0.0-1
  • ros-jazzy-rmw-implementation: 2.15.3-1 → 2.15.4-1
  • ros-jazzy-robot-calibration: 0.9.2-1 → 0.10.0-1
  • ros-jazzy-robot-calibration-msgs: 0.9.2-1 → 0.10.0-1
  • ros-jazzy-ros-babel-fish: 0.10.0-1 → 0.10.3-1
  • ros-jazzy-ros-babel-fish-test-msgs: 0.10.0-1 → 0.10.3-1
  • ros-jazzy-ros-workspace: 1.0.3-6 → 1.0.3-7
  • ros-jazzy-ros2-control: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-ros2-control-test-assets: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-ros2-controllers: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-ros2-controllers-test-nodes: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-ros2action: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2bag: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-ros2cli: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2cli-test-interfaces: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2component: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2controlcli: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-ros2doctor: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2interface: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2launch: 0.26.5-2 → 0.26.6-1
  • ros-jazzy-ros2lifecycle: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2lifecycle-test-fixtures: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2multicast: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2node: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2param: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2pkg: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2run: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2service: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2topic: 0.32.1-1 → 0.32.2-1
  • ros-jazzy-ros2trace: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-rosbag2: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-compression: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-compression-zstd: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-cpp: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-examples-cpp: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-examples-py: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-interfaces: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-performance-benchmarking: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-performance-benchmarking-msgs: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-py: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-storage: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-storage-default-plugins: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-storage-mcap: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-storage-sqlite3: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-test-common: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-test-msgdefs: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-tests: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosbag2-transport: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-rosidl-adapter: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-cli: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-cmake: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-generator-c: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-generator-cpp: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-generator-type-description: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-parser: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-pycommon: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-runtime-c: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-runtime-cpp: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-typesupport-fastrtps-c: 3.6.0-2 → 3.6.1-1
  • ros-jazzy-rosidl-typesupport-fastrtps-cpp: 3.6.0-2 → 3.6.1-1
  • ros-jazzy-rosidl-typesupport-interface: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-typesupport-introspection-c: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rosidl-typesupport-introspection-cpp: 4.6.4-1 → 4.6.5-1
  • ros-jazzy-rqt-controller-manager: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-rqt-joint-trajectory-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-rqt-topic: 1.7.2-2 → 1.7.3-1
  • ros-jazzy-rtabmap: 0.21.6-1 → 0.21.9-1
  • ros-jazzy-rtabmap-conversions: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-demos: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-examples: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-launch: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-msgs: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-odom: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-python: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-ros: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-rviz-plugins: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-slam: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-sync: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-util: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rtabmap-viz: 0.21.5-3 → 0.21.9-1
  • ros-jazzy-rviz-assimp-vendor: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-common: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-default-plugins: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-ogre-vendor: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-rendering: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-rendering-tests: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz-visual-testing-framework: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-rviz2: 14.1.5-1 → 14.1.6-1
  • ros-jazzy-sdformat-vendor: 0.0.7-1 → 0.0.8-1
  • ros-jazzy-shared-queues-vendor: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-sick-scan-xd: 3.5.0-1 → 3.6.0-1
  • ros-jazzy-slam-toolbox: 2.8.1-2 → 2.8.2-1
  • ros-jazzy-spatio-temporal-voxel-layer: 2.5.3-1 → 2.5.4-1
  • ros-jazzy-spinnaker-camera-driver: 2.0.20-1 → 3.0.0-1
  • ros-jazzy-spinnaker-synchronized-camera-driver: 2.0.20-1 → 3.0.0-1
  • ros-jazzy-sqlite3-vendor: 0.26.5-1 → 0.26.6-1
  • ros-jazzy-steering-controllers-library: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-stereo-image-proc: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-tf2: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-bullet: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-eigen: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-eigen-kdl: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-geometry-msgs: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-kdl: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-msgs: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-py: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-ros: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-ros-py: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-sensor-msgs: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-tf2-tools: 0.36.4-1 → 0.36.7-1
  • ros-jazzy-theora-image-transport: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-tile-map: 2.4.3-1 → 2.4.4-1
  • ros-jazzy-tracetools: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-tracetools-image-pipeline: 5.0.5-1 → 5.0.6-1
  • ros-jazzy-tracetools-launch: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-tracetools-read: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-tracetools-test: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-tracetools-trace: 8.2.2-1 → 8.2.3-1
  • ros-jazzy-transmission-interface: 4.20.0-1 → 4.21.0-1
  • ros-jazzy-tricycle-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-tricycle-steering-controller: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-tuw-geometry: 0.0.7-4 → 0.1.2-1
  • ros-jazzy-ur: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-ur-calibration: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-ur-client-library: 1.4.0-1 → 1.5.0-1
  • ros-jazzy-ur-controllers: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-ur-dashboard-msgs: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-ur-description: 2.4.5-1 → 3.0.0-1
  • ros-jazzy-ur-moveit-config: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-ur-msgs: 2.0.1-1 → 2.1.0-1
  • ros-jazzy-ur-robot-driver: 2.4.13-1 → 3.0.0-1
  • ros-jazzy-velocity-controllers: 4.16.0-1 → 4.18.0-1
  • ros-jazzy-yaml-cpp-vendor: 9.0.0-2 → 9.0.1-1
  • ros-jazzy-zstd-image-transport: 4.0.2-1 → 4.0.3-1
  • ros-jazzy-zstd-vendor: 0.26.5-1 → 0.26.6-1

Removed Packages [1]:

  • ros-jazzy-swri-prefix-tools

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:

  • Addisu Taddese
  • Aditya Pande
  • Alberto Tudela
  • Alejandro Hernandez
  • Alexander Gutenkunst
  • Alexey Merzlyakov
  • Apex.AI, Inc.
  • Audrow Nash
  • Bence Magyar
  • Benjamin Binder
  • Bernd Pfrommer
  • Blake Anderson
  • Brandon Ong
  • Brian Wilcox
  • Błażej Sowa
  • Carl Delsey
  • Carlos Orduno
  • Chittaranjan Srinivas Swaminathan
  • Chris Iverach-Brereton
  • Chris Lalancette
  • Christian Henkel
  • Christian Rauch
  • Christoph Hellmann Santos
  • Christophe Bedard
  • Dave Coleman
  • David V. Lu!!
  • Denis Stogl
  • Dirk Thomas
  • Dorian Scholz
  • Eclipse Foundation, Inc.
  • Emerson Knapp
  • Felix Exner
  • Felix Ruess
  • Foxglove
  • Francisco Martin Rico
  • Francisco Martín Rico
  • G.A. vd. Hoorn
  • Geoffrey Biggs
  • George Stavrinos
  • George Todoran
  • Guilhem Saurel
  • Hans-Joachim Krauch
  • Henning Kayser
  • Ivan Paunovic
  • Jean-Pierre Busch
  • Jordan Palacios
  • Jose Luis Blanco-Claraco
  • Jose Mastrangelo
  • Kenji Brameld
  • Kevin Hallenbeck
  • Lovro Ivanov
  • Luis Camero
  • M. Fatih Cırıt
  • Mamoru Sobue
  • Markus Bader
  • Matej Vargovcik
  • Mathieu Labbe
  • Michael Ferguson
  • Michael Görner
  • Michael Jeronimo
  • Michael Orlov
  • Micho Radovnikovich
  • Miguel Company
  • Miguel Ángel González Santamarta
  • Mike Lautman
  • Mike Purvis
  • Mohammad Haghighipanah
  • MoveIt Release Team
  • Peter David Fagan
  • Pradheep Padmanabhan
  • ROS Tooling Working Group
  • RT Corporation
  • Raphael Hagmanns
  • Raymond Chow
  • Rob Fisher
  • Roni Kreinin
  • Scott K Logan
  • Shane Loretz
  • Southwest Research Institute
  • Stefan Fabian
  • Steve Macenski
  • Takagi, Isamu
  • Tarik Viehmann
  • Tim Clephas
  • Tyler Weaver
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • William Woodall
  • Yutaka Kondo
  • ijnek
  • kminoda
  • miguel
  • mitsudome-r
  • pradyum
  • rkreinin
  • rostest
  • ruess

Enjoy! :jazzy:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-and-patch-release-3-for-jazzy-jalisco-2024-12-23/41347

ROS Discourse General: New static archives for ROS and Gazebo Answers

Answered questions from ROS and Gazebo Answers were previously migrated to Robotics Stack Exchange.

In order to preserve the unmigrated questions we have exported the remaining data from each site instance and rendered them in static sites.

As the year comes to a close we are now switching over to the static archives. Questions which were migrated to Stack Exchange will be redirected to the question’s new home. Whereas those which were not will be shown on a static page.

I will update the thread here when the DNS cut-over is complete, and again when the old Askbot sites are taken offline. Due to the nature of DNS, some individuals may continue to see DNS responses including the old server locations and thus see the old Askbot sites or error pages.

Please do not report this as it is an expected and inevitable part of this migration. Once we are confident that DNS changes have fully propagated we’ll request information from anyone still experiencing unexpected DNS resolution.

6 posts - 5 participants

Read full topic

[WWW] https://discourse.ros.org/t/new-static-archives-for-ros-and-gazebo-answers/41346

ROS Discourse General: ROS News for the Week of December 23rd, 2024 :snowman:

ROS News for the Week of December 23rd, 2024 :snowman:


wrap
Last week I may have said I wouldn’t be impressed with a robot Christmas video until I see a robot wrap a present. It appears Acumino delivered (just like Santa :santa:). See this video and a ton of other great holiday robot videos in our Robotics Christmas Videos 2024 thread.


image

The OSRA is wrapping up it’s first year (actually 8 months) of operation. @gbiggs put together an OSRA activity recap for 2024.

The OSRA’s next big task is reforming our ROS Enhancement Proposal process and we really could use some feedback from the community,


image

Just in time for the holidays Duatic AG has released a new robot, the DynaArm, that supports ROS 2 out of the box. Source code available here.


image

A few weeks ago @abaeyens lent the ROS core team a hand by writing some fantastic documentation for ROS 2 integration testing. This week he’s back with a new prototype / proof of concent tool to run ROS 2 integration tests in parallel called testjob_coordinator. Testing may not produce exciting robot videos, but it is really important, and this new tool could save a lot of us a lot of valuable time!


Events

News

ROS

Got a Minute? :mantelpiece_clock:

There are literally hundreds of ROS 2 repositories that have pull requests that need a review! Anyone in the ROS community can do a review, and we need second reviewers to get pull requests out the door. Please lend your expertise to the project! Even a quick scan and a LGTM is helpful.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-december-23rd-2024/41304

ROS Discourse General: Best Robotics Platform for development and demos

0

I’m looking to buy two robotic platforms to develop algorithms and make demos. I prefer not to use robotic arms.

The robots should move outdoors and indoors, and they are sold by companies that can support them if there is an HW issue. One last point is that the integration should be easy.

I have already seen Clearpath, Unitree, Pal, and Robotnik. Do you have any more suggestions?

9 posts - 9 participants

Read full topic

[WWW] https://discourse.ros.org/t/best-robotics-platform-for-development-and-demos/41302

ROS Discourse General: Interoperability Special Interest Group skipping January 2025

Due to proximity to the holidays, we will be skipping the January 2025 session of the Interoperability Special Interest Group.

We will resume the regularly scheduled sessions on 6 February 2025.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/interoperability-special-interest-group-skipping-january-2025/41281

ROS Discourse General: Robotics Christmas Videos 2024

Hi! I noticed that no thread was started yet to share robotic christmas videos of 2024!

IEEE have started their latest video list already here:

For anyone who is winding down already for the holidays, please share any you have encountered so far :christmas_tree:

Happy holidays everyone!

7 posts - 6 participants

Read full topic

[WWW] https://discourse.ros.org/t/robotics-christmas-videos-2024/41261

ROS Discourse General: What is in scope for an Enhancement Proposal?

The OSRA’s Technical Committee on Enhancement Proposal Processes has been working over the past few months to produce a replacement for the current ROS Enhancement Proposal (REP) process, which is now severely out of date and doesn’t work with our current tools (we don’t, for example, have the mailing list it requires anymore). The TC has been looking at what no longer works with the current REP process, as well as what many other organisations with similar processes do.

As part of this work, the TC has run into that most difficult of questions: what is in scope? In other words, when do you need to send in an Enhancement Proposal and follow the prescribed process to get it approved/accepted, and when can you just go ahead and submit a PR?

So far we’ve come up with some obvious ones that we think might be in scope, like making significant changes to an external API. However this is something of a braintstorming exercise, and the more brains doing some storming, the better.

So, now that most of us are moving into a week or two of not-working-that-much, I’d like to hear your thoughts. For what should you need to follow a REP-like process? What should never be in scope? What is in the grey zone and would need discussion on a case-by-case basis?

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/what-is-in-scope-for-an-enhancement-proposal/41254

ROS Discourse General: OSRA TGC meeting minutes for November, 2024

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 21st of November, 2024, were approved in the December meeting and are now available in the official minutes repository. You can find the complete minutes here.

The TGC received the monthly project and technical committee updates, including the success of in-person PMC meetings at ROSCon, the news that Open-RMF has switched to using Zenoh, and the Infrastructure team working to move to Ubuntu 24.04.

Of particular note in this meeting, the TC on Enhancement Proposal Processes has started dealing with the thorny question of “what is in scope for an Enhacement Proposal?”

In a follow-up to an item from the October meeting, the OSRF Board of Directors decided to reject the proposal to move the Nexus project under the Open-RMF PMC for the time being. This decision was made because the Board wants the Open-RMF project to concentrate on making its existing feature set robust before expanding the scope of the project.

The next TGC meeting will take place in January, 2025. The minutes of the December meeting should be approved in that meeting and posted publicly shortly thereafter.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-november-2024/41252

ROS Discourse General: OSRA activity recap for 2024

As 2024 draws to a close, we’re happy to say that the OSRA has had a successful first eight months of operation. Although we still have much to do with spinning up all the different bits of the OSRA, in the past eight months we have set up the Technical Governance Committee (TGC) and four Project Management Committees (PMCs) for ROS, Gazebo, Open-RMF and Infrastructure. The TGC has set up one Special Interest Group (SIG) and two Technical Committees (TCs), one of which (on the use of generative AI tools) has already completed its work.

The TGC has discussed several technical matters of relevance to the projects that were brought up by the TGC members. Some of these have been resolved, and some are on-going. The TGC is looking forward to an even more productive 2025 with several important matters to discuss, not the least of which is to begin applying OSRA membership dues to project requests.

The PMCs are starting to grow, too. Both the ROS and the Gazebo PMCs are beginning to mentor new Committers and PMC Members from the community.

For more details, pelase see the attached PDF.

OSRA Activity Recap - March 2024 Launch To-Date.pdf (106.9 KB)

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/osra-activity-recap-for-2024/41251

Wiki: TullyFoote/TestPlanetRSS (last edited 2014-09-25 22:49:53 by TullyFoote)

Except where otherwise noted, the ROS wiki is licensed under the
Creative Commons Attribution 3.0