Current participants as of April 02, 2025 12:16 PM (UTC):
ASL ETHZ, Achu Wilson, CAR: Components, Agents, and Robots with Dynamic Languages, David Hodo, Fawkes, Isaac Saito, John Stowers, Mat Sadowski Blog, Michael Ferguson, MobileWill, MoveIt!, NooTriX, Open Source Robotics Foundation, PAL Robotics blog, Pi Robot, ROS Discourse General, ROS Industrial, ROS news, ROSVirtual, Robbie The Robot, Robots For Robots, Sachin Chitta's Blog, TORK, William Woodall, Yujin R&D, mobotica,

Want your blog to be on the awesome planet ROS ?

If you are a ROS developer/user and you blog about it, ROS wants those contributions on this page ! All you need for that to happen is:

• have an RSS/Atom blog (no Tweeter/Facebook/Google+ posts)
• open a pull request on planet.ros tracker indicating your name and your RSS feed/ATOM url. (You can just edit the file and click "Propose File Change" to open a pull request.)
• make your ROS related posts tagged with any of the following categories: "ROS", "R.O.S.", "ros", "r.o.s."

Warnings

For security reasons, html iframe, embed, object, javascript will be stripped out. Only Youtube videos in object and embed will be kept.

Guidelines

Planet ROS is one of the public faces of ROS and is read by users and potential contributors. The content remains the opinion of the bloggers but Planet ROS reserves the right to remove offensive posts.

Blogs should be related to ROS but that does not mean they should be devoid of personal subjects and opinions : those are encouraged since Planet ROS is a chance to know more about ROS developers.

Posts can be positive and promote ROS, or constructive and describe issues but should not contain useless flaming opinions. We want to keep ROS welcoming :)

ROS covers a wide variety of people and cultures. Profanities, prejudice, lewd comments and content likely to offend are to be avoided. Do not make personal attacks or attacks against other projects on your blog.

Suggestions ?

If you find any bug or have any suggestion, please file a bug on the planet.ros tracker.

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 27th of February, 2025, were approved in the March meeting and are now available in the official minutes repository. You can find the complete minutes here, as well as a Markdown version below. The Markdown version is experimental so please excuse any formatting problems and errors; the PDF version is the official version.

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

---

TECHNICAL GOVERNANCE COMMITTEE

MEETING MINUTES

27 FEB 2025 / 14:00-15:30 UTC / VIRTUAL VIA ZOOM

ATTENDEES

OSRF:

• Kat Scott (Developer Advocate)
• Vanessa Yamzon Orsi (Secretary)
• Vicky Brasseur (OSRA Governance Advisor)

OSRA Delegates/TGC Reps:

• Bence Magyar (ros-controls PMC Lead)
• Carlos Aguero, (Gazebo Lead Proxy)
• Clara Berendesen (Infra PMC Representative)
• Daniel Gordon (Gold Rep, Huawei)
• David Lu!! (Individual Rep)
• Hemal Shah (Platinum Rep, NVIDIA)
• Maria Vergo (Silver Rep, ROS-I)
• Michael Carroll (ROS PMC Interim Lead)
• Michael Grey (Open-RMF)
• Michel Hidalgo (Silver Rep, Ekumen)
• Steve Peters (Gazebo)
• Steven! Ragnarok (Infrastructure PMC Lead)
• Tully Foote (Platinum Rep, Intrinsic)
• Zhaoyuan Cheng (Platinum Rep, Qualcomm)

OSRA Observers

• Carmelo Di Franco (Aitronik)
• Christian Henkel (Bosch)
• Henning Kayser (PickNik)
• Nick Hehr (Viam)
• Tom Panzarella (Seegrid)
• Todd Sutton (Zachry)

AGENDA

Vanessa Yamzon Orsi, TGC Secretary (filling in for the TGC Chair) called the meeting to order at 15:04 on 27 Feb 2025 UTC

Existing Business

1. Confirmation of minutes of meeting TGC-20250123-Regular
   • Approved by consensus
2. Project reports
   • Project update: ROS
     • Presented by Michael Carroll, PMC Lead
       • Transition work in progress as Michael took over as interim project lead from Chris Lalancette.
       • Main priority is wrapping up RMW Zenoh as a Tier 1 middleware. Final steps on security implementation, CI and build farm are in progress. Aiming for completion before feature freeze on April 7 for the Kilted release.
       • pixi and Conda migration - for Kilted and Rolling going forward, pixi will be the recommended installation procedure for ROS on Windows. We are seeing community excitement around this, and we are happy to report that the process is much better and we are getting support from the folks at prefix.dev who develop pixi.
       • eProsima is wrapping up the renaming of Fast-RTPS to FastDDS in preparation of landing a new version of FastDDS in Kilted.
       • Tomoya and Sony are working on action introspection to record ROSbag actions and replay them, a valuable feature for users with action-heavy workflows like Nav2.
       • The Client Library Working Group has a couple of contributions such as a multi-threaded executor starvation fix and an rclpy events executor which improves python performance by an order of magnitude.
       • Kilted timeline reminder: Feature freeze on April 7 with events in between including testing and tutorial party before final release on May 23, 2025.
   • Project update: Gazebo
     • Presented by Steve Peters, PMC Member on behalf of the PMC Lead
       • Carlos Aguero (Honu) will serve as interim PMC lead while Addisu Taddese (Intrinsic) is out on personal leave.
       • External contributions: generating 3D meshes from a smartphone and then making a Gazebo world from that, features from Gazebo Classic that were ported by community members such as visualizing frustums for cameras and also using the physics engine to calculate ray intersection.
       • Recent features announced at community meeting: updated automatic inertial calculation feature to auto calculate density from specifying the mass of a link.
       • Conda for Windows support: Gazebo’s Windows and CI machines have been switched to use Conda and pixi instead of vcpg.
       • Roadmap item: continuing prototyping work on using Xeno with Gz transport.
       • Several GSoC projects have been proposed: Migrating from QT 5 to 6, deprecating the Gz launch package which is mostly redundant with ROS 2 launch.
       • The PMC has nominated Saurabh Kamat (github.com/sauk2) as a project committer; he is a great contributor and is now in the mentorship phase under Carlos Aguero.
   • Project update: Open-RMF
     • Presented by Michael Grey, PMC Lead
       • One of the large ongoing efforts is the development of a workflow execution framework, particularly targeting workflow diagrams that can represent multi-agent interactions. The execution framework is finished, now working a serialized format to represent the workflow.
       • Close to having support for buffer elements - elements within the workflow that can store data in flight or which needs to be retained during the lifespan of the workflow.
       • Quality of life improvements to the site editor UI around the scenarios concept, currently an experimental feature.
       • Moved on async capabilities for rclrs
         • Discussion on rcls as the library of choice for Open-RMF implementation.
       • The PMC initiated a biweekly Open-RMF community forum. This is an open-format, no agenda meeting. Community members may ask questions and the PMC representatives will answer.
   • Project update: Infrastructure
     • Presented by Steven! Ragnarok, PMC Lead
       • Primary mission right now is to transition all of our infrastructure hosts from Ubuntu 20.04 to 24.04 before the end of community support for 20.04. Contingency plans in place for support in the case we don’t make the cutoff. The priority is to move the ROS 2 buildfarm by mid-March to prepare for the work on ROS 2 Kilted (Kaiju).
       • We had the first release of ROS build farm python modules in some time. Both the Infra team and community have been instructed to use them directly from the main development branch, but this was done so that other released packages can depend on it.
       • All other resources focused on maintenance.
   • Project update: ROS Controls
     • Presented by Bence Magyar, PMC Lead
       • The PMC has been running a fortnightly meeting with leads and contributors.
       • Working with companies upstreaming specialized or rugged versions of controllers such as the scaled joint trajectory controller that Universal Robot worked on.
       • Working on adding the joint functionality at the framework and not the controller level.
       • Recurring discussions are in place over introducing a real time-friendly high frequency logging or introspection tool to support running in the kHz range. Opted to adopt path statistics.
       • Several depreciations are marked for removal for the ROS 2 L-release.
       • Call for contribution to the PR regarding the joint limiting topic currently on Discourse.
3. Existing Business

   • Status of SIGs/TCs

     • Technical Committee on Enhancement Proposal Processes

       • Goal: Upgrade and improvements over REP
       • Chair: Geoff Biggs (presented by Vanessa Yamzon Orsi on behalf of Geoff Biggs)
       • Members: PMC Leads
       • Update:
         • Draft of scope and process is in progress, aiming to circulate to the TGC for review in the March 2025 meeting, however there is a possibility of an upcoming extension request
         • Items in discussion: platform for collecting, reviewing and discussing enhancement proposals, process for handling backlog

     • SIG on Interoperability

       • Chair: Michael Grey
       • In this month’s meeting, Aaron Chong (Intrinsic) presented on recent developments on RMF-web that improves modularity.

   • Results of vote to recommend adoption of GAI policy

     • The received votes are as follows:
       - 5 for, 1 abstention; quorum was not reached and therefore the motion is lost.
     • Discussion opened regarding two topics:
       • Broader discussion on voting and how to encourage more votes
       • Specific discussion regarding why this particular motion did not attain the required quorum.
     • Takeaways:
       • Explore increased asynchronous communication methods to give members more time to study and discuss issues.
       • Explore options for asynchronous voting to remove hindrances from live voting during TGC meetings, consider methods for preserving discussions and voting records by matter.
       • More explicit calls to action in communications and increase in follow-ups.
       • Review charter specifications and amend them if necessary.

   • Report on progress on federated mirroring

     • The effort falls under discussions within the OSRA as to how we could do more to make ROS and other project resources more available to those in the community who are not able to reliably access centralized resources like GitHub, ROS wiki, and other documentation sites hosted in the United States.
     • We have existing guides but some information is outdated. We need a new and more comprehensive guide with expanded information and a way to verify that a mirror of a repository matches what is available.
     • Currently assessing tools that would make this possible, and further work on building this guide is on the Infra project team’s radar.
     • Discussions were had regarding the timeline and resources needed vs other Infra team projects, approach to project execution, and impact on ROS metrics and assessing community growth.

New Business

1. Welcome to new TGC members
   Several new members are joining the TGC from this meeting:
   • Bence Magyar (Locus) - ROS Controls Project Leader
   • Clara Berendsen (Ekumen) - Infrastructure PMC Representative
   • Daniel Gordon (Huawei) - Gold Representative
   • Christian Henkel (Bosch) - Gold Representative
   • Maria Carolina Vergo (ROS-I) - Silver Representative

Other Items

• None

Adjournment - Vanessa Yamzon Orsi adjourned the meeting at 15:25 UTC.

ACTION ITEMS

1. The meeting minutes will be circulated to the TGC for review and approval before the next meeting by the TGC Chair.
2. Steven! Ragnarok (Infra PMC Lead) to send a summary of the federated mirroring progress report to the TGC.
3. The TGC Chair will lead the research on async communication and voting mechanism improvements.

1 post - 1 participant

Read full topic

The next ROS Deliberation Community Group meeting will be on 2025-04-07T15:00:00Z UTC.

Google Meet link: https://meet.google.com/njs-ieym-dgk

Agenda:

• Deliberation tool spotlight:
  • Looking for volunteers! Please let us know if you’re interested in presenting for ~5-10 minutes.
• European Robotics Forum (ERF) recap
  • Workshop: Advancing AI-Powered Robotic Cognition, Deliberation and Learning for Real-World Applications
• Open discussion (topics welcome!)

Feel free to propose additional agenda items, join the mailing list, or the Discord server.

- Sebastian

1 post - 1 participant

Read full topic

Hi, this will be a long post!

I’m a late ROS 1 → 2 transitioner with a research and teaching background. I learned ROS long ago by myself and was also taught it at under and grad level. However, when I arrived at ROS 2, I had a hard time adapting, even though I had plenty of experience with ROS. After a year, I have thought deeply about the reasons and arrived at two main reasons:

1. The tutorials and onboarding experience.
2. There is a lack of established practices.

The second is getting better every day, and I think that it’s a matter of convergence for the community. However, the first is more concerning, in my opinion. Over the last months, I have gathered a series of points that could be improved and I would like to share it with all of you, get your feedback, and possibly your help for improving the tutorials and general docs. The aim of this post is to work towards a general tutorial upgrade to ease the entry-level experience for users.

Why? ROS tutorials are the entry point for both newcomers and transitioners. From our teaching experience, if the complexity gets overwhelming, students will simply avoid ROS at all costs. I have discussed this issue with people from different backgrounds and experiences and agree that, currently, it’s difficult to approach ROS 2 unless you have been an early developer.

Why now? ROS (1) EOL has arrived, and a lot of transitioners will use the tutorials to look for differences between the two major versions. Any undergraduate and graduate education that didn’t transition will do it before the next semester starts.

How? So far, I have gathered in this document (EDIT: Please, even if you leave a comment in the GDocs, write also a comment on this post to keep it alive) a list of improvement points with a clear action that could be turned into a GitHub issue in the docs repo. However, before flooding the repo, I would like to have some initial feedback from the community, hence this post. I think that some organization such as a work group could also be interesting.

Next steps So far, I would appreciate some feedback on the general idea and the specific ideas in the document linked above (it has commenter permissions). I would also appreciate any other ideas in this post. Finally, ideas on how to organize the workload and a possible work group are also appreciated. After that, we could move on to the actual work!

Just as a disclaimer, this post is not a complaint. I understand that the whole community puts a lot of effort into gradually improving all the content. My objective is to give it a push so everyone can have an easy approach to using and contributing to this community.

5 posts - 3 participants

Read full topic

Dear ROS Community Members,

We are excited to announce that we are crafting a standard message representation for ROS2 using AsyncAPI. A draft is already available on GitHub, and we warmly invite the ROS community to join us in refining this specification. Your input is invaluable, and we encourage you to participate in the ongoing discussions.

Right now, we have developed an AsyncAPI binding for ROS2, and there’s a vibrant conversation happening on GitHub. To enhance collaboration, we’re planning to hold an open discussion session. To help us find a time that suits everyone, please indicate your availability using the Microsoft Forms link below:

Indicate Your Availability Here

Slot 1: 2025-04-08T12:00:00Z UTC→2025-04-08T13:00:00Z UTC

Slot 2: 2025-04-09T12:00:00Z UTC→2025-04-09T13:00:00Z UTC

Slot 3: 2025-04-10T08:00:00Z UTC→2025-04-10T09:00:00Z UTC

Slot 4: 2025-04-10T14:00:00Z UTC→2025-04-10T15:00:00Z UTC

If you’re interested in learning more about AsyncAPI and its significance for ROS2 users, we invite you to watch the ROSCon DE talk we presented last year:

Watch the ROSCon DE Talk - PDF
( @destogl would you please help us access the video recording, please?)

Join the discussion on GitHub:

AsyncAPI Specification Draft on GitHub

We look forward to your contributions and to meeting you all soon!

Best regards,

Florian

This Communication is part of the aerOS project that has received funding from the European Union’s Horizon Europe research and innovation programme under grant agreement Nº101069732

4 posts - 4 participants

Read full topic

Community Page

Meeting Link

Calendar Link

2025-04-03T15:00:00Z UTC

The site editor is a tool in the Open-RMF project that allows users to sketch a facility in 3D and specify the mobile robot traffic rules within it.

A common requirement when designing the operations within a facility is the need to consider many different configurations of robots. You may want to see what happens when they are positioned differently or have different properties. You might see positive or negative impacts on the effectiveness or efficiency of your operations under the different circumstances.

A recently introduced feature to the site editor is the concept of Scenarios which allows users to create inter-related variations of scenarios within the same facility. Scenarios can have parent/child relationships with each other where child scenarios inherit the characteristics of parent scenarios and then introduce their own modifications. This creates branching worlds where modifications to a parent scenario will carry over into the child scenarios, while child scenarios can diverge from each other.

At this month’s session, Xiyu Oh will introduce us to the scenarios feature.

1 post - 1 participant

Read full topic

Hi Everyone,
The JetsonAI Research Group is meeting tomorrow (4/1/25) at 9AM PST.

• Microsoft Teams - Meeting Link
• Meeting ID: 264 770 145 196
• Passcode: Uwbdgj

Hope to see you there,

2 posts - 2 participants

Read full topic

We’re happy to announce a new Humble release!

This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)

Package Updates for Humble

Added Packages [27]:

• ros-humble-apriltag-detector-dbgsym: 3.0.1-1
• ros-humble-apriltag-tools: 3.0.1-1
• ros-humble-apriltag-tools-dbgsym: 3.0.1-1
• ros-humble-dynamixel-hardware-interface: 1.4.0-1
• ros-humble-dynamixel-hardware-interface-dbgsym: 1.4.0-1
• ros-humble-dynamixel-interfaces: 1.0.1-1
• ros-humble-dynamixel-interfaces-dbgsym: 1.0.1-1
• ros-humble-etsi-its-denm-ts-coding: 3.1.0-1
• ros-humble-etsi-its-denm-ts-coding-dbgsym: 3.1.0-1
• ros-humble-etsi-its-denm-ts-conversion: 3.1.0-1
• ros-humble-etsi-its-denm-ts-msgs: 3.1.0-1
• ros-humble-etsi-its-denm-ts-msgs-dbgsym: 3.1.0-1
• ros-humble-kinova-gen3-lite-moveit-config: 0.2.3-1
• ros-humble-mecanum-drive-controller: 2.43.0-1
• ros-humble-mecanum-drive-controller-dbgsym: 2.43.0-1
• ros-humble-mola-gnss-to-markers: 0.1.0-1
• ros-humble-mola-gnss-to-markers-dbgsym: 0.1.0-1
• ros-humble-performance-test: 2.3.0-1
• ros-humble-performance-test-dbgsym: 2.3.0-1
• ros-humble-pmb2-rgbd-sensors: 4.11.0-1
• ros-humble-rmw-desert: 1.0.4-1
• ros-humble-rmw-desert-dbgsym: 1.0.4-1
• ros-humble-synapticon-ros2-control: 0.1.2-1
• ros-humble-synapticon-ros2-control-dbgsym: 0.1.2-1
• ros-humble-tiago-rgbd-sensors: 4.9.0-1
• ros-humble-webots-ros2-crazyflie: 2025.0.0-2
• ros-humble-webots-ros2-husarion: 2025.0.0-2

Updated Packages [535]:

• ros-humble-ackermann-steering-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-ackermann-steering-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-actionlib-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-actionlib-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-admittance-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-admittance-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-ament-clang-format: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-clang-tidy: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-clang-format: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-clang-tidy: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-copyright: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-cppcheck: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-cpplint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-flake8: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-lint-cmake: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-mypy: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-pclint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-pep257: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-pycodestyle: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-pyflakes: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-uncrustify: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cmake-xmllint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-copyright: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cppcheck: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-cpplint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-flake8: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-lint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-lint-auto: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-lint-cmake: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-lint-common: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-mypy: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-pclint: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-pep257: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-pycodestyle: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-pyflakes: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-uncrustify: 0.12.11-1 → 0.12.12-1
• ros-humble-ament-xmllint: 0.12.11-1 → 0.12.12-1
• ros-humble-apriltag: 3.4.2-1 → 3.4.3-1
• ros-humble-apriltag-dbgsym: 3.4.2-1 → 3.4.3-1
• ros-humble-apriltag-detector: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-detector-mit: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-detector-mit-dbgsym: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-detector-umich: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-detector-umich-dbgsym: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-draw: 2.1.0-1 → 3.0.1-1
• ros-humble-apriltag-draw-dbgsym: 2.1.0-1 → 3.0.1-1
• ros-humble-automatika-ros-sugar: 0.2.7-1 → 0.2.9-1
• ros-humble-automatika-ros-sugar-dbgsym: 0.2.7-1 → 0.2.9-1
• ros-humble-autoware-cmake: 1.0.0-2 → 1.0.1-1
• ros-humble-autoware-lanelet2-extension: 0.6.2-1 → 0.6.3-1
• ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.2-1 → 0.6.3-1
• ros-humble-autoware-lanelet2-extension-python: 0.6.2-1 → 0.6.3-1
• ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.2-1 → 0.6.3-1
• ros-humble-autoware-lint-common: 1.0.0-2 → 1.0.1-1
• ros-humble-bicycle-steering-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-bicycle-steering-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-camera-calibration: 3.0.6-1 → 3.0.7-1
• ros-humble-camera-calibration-parsers: 3.1.10-1 → 3.1.11-1
• ros-humble-camera-calibration-parsers-dbgsym: 3.1.10-1 → 3.1.11-1
• ros-humble-camera-info-manager: 3.1.10-1 → 3.1.11-1
• ros-humble-camera-info-manager-dbgsym: 3.1.10-1 → 3.1.11-1
• ros-humble-camera-info-manager-py: 3.1.10-1 → 3.1.11-1
• ros-humble-clearpath-common: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-config: 1.1.0-1 → 1.2.0-1
• ros-humble-clearpath-config-live: 1.0.0-1 → 1.2.0-1
• ros-humble-clearpath-control: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-customization: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-description: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-desktop: 1.0.0-1 → 1.2.0-1
• ros-humble-clearpath-generator-common: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-generator-common-dbgsym: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-manipulators: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-manipulators-description: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-mounts-description: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-platform-description: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-sensors-description: 1.1.1-1 → 1.2.0-1
• ros-humble-clearpath-viz: 1.0.0-1 → 1.2.0-1
• ros-humble-coal: 3.0.0-1 → 3.0.1-1
• ros-humble-coal-dbgsym: 3.0.0-1 → 3.0.1-1
• ros-humble-common-interfaces: 4.2.4-1 → 4.8.0-1
• ros-humble-control-msgs: 4.7.0-1 → 4.8.0-1
• ros-humble-control-msgs-dbgsym: 4.7.0-1 → 4.8.0-1
• ros-humble-controller-interface: 2.48.0-1 → 2.49.0-1
• ros-humble-controller-interface-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-controller-manager: 2.48.0-1 → 2.49.0-1
• ros-humble-controller-manager-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-controller-manager-msgs: 2.48.0-1 → 2.49.0-1
• ros-humble-controller-manager-msgs-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-dataspeed-can: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-msg-filters: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-msgs: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-msgs-dbgsym: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-tools: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-tools-dbgsym: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-usb: 2.0.5-1 → 2.0.6-1
• ros-humble-dataspeed-can-usb-dbgsym: 2.0.5-1 → 2.0.6-1
• ros-humble-depth-image-proc: 3.0.6-1 → 3.0.7-1
• ros-humble-depth-image-proc-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-depthai: 2.29.0-1 → 2.30.0-1
• ros-humble-depthai-bridge: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-bridge-dbgsym: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-dbgsym: 2.29.0-1 → 2.30.0-1
• ros-humble-depthai-descriptions: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-examples: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-examples-dbgsym: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-filters: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-filters-dbgsym: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-ros: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-ros-driver: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-ros-driver-dbgsym: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-ros-msgs: 2.10.5-1 → 2.11.2-1
• ros-humble-depthai-ros-msgs-dbgsym: 2.10.5-1 → 2.11.2-1
• ros-humble-diagnostic-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-diagnostic-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-diff-drive-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-diff-drive-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-dynamixel-sdk: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-sdk-custom-interfaces: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-sdk-custom-interfaces-dbgsym: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-sdk-dbgsym: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-sdk-examples: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-sdk-examples-dbgsym: 3.7.60-1 → 3.8.2-1
• ros-humble-dynamixel-workbench: 2.2.3-1 → 2.2.4-1
• ros-humble-dynamixel-workbench-msgs: 2.0.3-1 → 2.1.0-1
• ros-humble-dynamixel-workbench-msgs-dbgsym: 2.0.3-1 → 2.1.0-1
• ros-humble-dynamixel-workbench-toolbox: 2.2.3-1 → 2.2.4-1
• ros-humble-dynamixel-workbench-toolbox-dbgsym: 2.2.3-1 → 2.2.4-1
• ros-humble-effort-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-effort-controllers-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-eigenpy: 3.8.2-1 → 3.10.3-1
• ros-humble-eigenpy-dbgsym: 3.8.2-1 → 3.10.3-1
• ros-humble-etsi-its-cam-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-ts-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cam-ts-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-conversion-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cpm-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cpm-ts-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cpm-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cpm-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-denm-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-denm-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-denm-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-denm-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-denm-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-mapem-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-mapem-ts-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-mapem-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-mapem-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-mapem-ts-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-messages: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-msgs-utils: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-primitives-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-rviz-plugins: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-rviz-plugins-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-spatem-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-spatem-ts-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-spatem-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-spatem-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-spatem-ts-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-vam-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-vam-ts-coding-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-vam-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-vam-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-humble-etsi-its-vam-ts-msgs-dbgsym: 3.0.0-1 → 3.1.0-1
• ros-humble-ffmpeg-encoder-decoder: 1.0.1-2 → 2.0.0-1
• ros-humble-ffmpeg-encoder-decoder-dbgsym: 1.0.1-2 → 2.0.0-1
• ros-humble-ffmpeg-image-transport: 1.1.2-1 → 2.0.1-1
• ros-humble-ffmpeg-image-transport-dbgsym: 1.1.2-1 → 2.0.1-1
• ros-humble-ffmpeg-image-transport-tools: 1.1.0-1 → 2.1.1-1
• ros-humble-ffmpeg-image-transport-tools-dbgsym: 1.1.0-1 → 2.1.1-1
• ros-humble-force-torque-sensor-broadcaster: 2.41.0-1 → 2.43.0-1
• ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-forward-command-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-forward-command-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-geometry-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-geometry-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-gpio-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-gpio-controllers-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-gripper-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-gripper-controllers-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-hardware-interface: 2.48.0-1 → 2.49.0-1
• ros-humble-hardware-interface-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-hardware-interface-testing: 2.48.0-1 → 2.49.0-1
• ros-humble-hardware-interface-testing-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-hls-lfcd-lds-driver: 2.0.4-3 → 2.1.0-1
• ros-humble-hls-lfcd-lds-driver-dbgsym: 2.0.4-3 → 2.1.0-1
• ros-humble-ign-ros2-control: 0.7.11-1 → 0.7.12-1
• ros-humble-ign-ros2-control-dbgsym: 0.7.11-1 → 0.7.12-1
• ros-humble-ign-ros2-control-demos: 0.7.11-1 → 0.7.12-1
• ros-humble-ign-ros2-control-demos-dbgsym: 0.7.11-1 → 0.7.12-1
• ros-humble-image-common: 3.1.10-1 → 3.1.11-1
• ros-humble-image-pipeline: 3.0.6-1 → 3.0.7-1
• ros-humble-image-proc: 3.0.6-1 → 3.0.7-1
• ros-humble-image-proc-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-image-publisher: 3.0.6-1 → 3.0.7-1
• ros-humble-image-publisher-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-image-rotate: 3.0.6-1 → 3.0.7-1
• ros-humble-image-rotate-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-image-transport: 3.1.10-1 → 3.1.11-1
• ros-humble-image-transport-dbgsym: 3.1.10-1 → 3.1.11-1
• ros-humble-image-view: 3.0.6-1 → 3.0.7-1
• ros-humble-image-view-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-imu-sensor-broadcaster: 2.41.0-1 → 2.43.0-1
• ros-humble-imu-sensor-broadcaster-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-joint-limits: 2.48.0-1 → 2.49.0-1
• ros-humble-joint-limits-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-joint-state-broadcaster: 2.41.0-1 → 2.43.0-1
• ros-humble-joint-state-broadcaster-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-joint-trajectory-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-joint-trajectory-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-kinova-gen3-6dof-robotiq-2f-85-moveit-config: 0.2.2-1 → 0.2.3-1
• ros-humble-kinova-gen3-7dof-robotiq-2f-85-moveit-config: 0.2.2-1 → 0.2.3-1
• ros-humble-kitti-metrics-eval: 1.6.0-1 → 1.6.3-1
• ros-humble-kitti-metrics-eval-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-kortex-api: 0.2.2-1 → 0.2.3-1
• ros-humble-kortex-bringup: 0.2.2-1 → 0.2.3-1
• ros-humble-kortex-description: 0.2.2-1 → 0.2.3-1
• ros-humble-kortex-driver: 0.2.2-1 → 0.2.3-1
• ros-humble-kortex-driver-dbgsym: 0.2.2-1 → 0.2.3-1
• ros-humble-launch: 1.0.7-1 → 1.0.8-1
• ros-humble-launch-pal: 0.10.0-1 → 0.11.0-1
• ros-humble-launch-pytest: 1.0.7-1 → 1.0.8-1
• ros-humble-launch-ros: 0.19.8-1 → 0.19.9-1
• ros-humble-launch-testing: 1.0.7-1 → 1.0.8-1
• ros-humble-launch-testing-ament-cmake: 1.0.7-1 → 1.0.8-1
• ros-humble-launch-testing-ros: 0.19.8-1 → 0.19.9-1
• ros-humble-launch-xml: 1.0.7-1 → 1.0.8-1
• ros-humble-launch-yaml: 1.0.7-1 → 1.0.8-1
• ros-humble-libcurl-vendor: 3.1.2-1 → 3.1.3-1
• ros-humble-mcap-vendor: 0.15.13-1 → 0.15.14-1
• ros-humble-mcap-vendor-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-message-filters: 4.3.5-1 → 4.3.6-1
• ros-humble-message-filters-dbgsym: 4.3.5-1 → 4.3.6-1
• ros-humble-metavision-driver: 2.0.0-1 → 2.0.1-1
• ros-humble-metavision-driver-dbgsym: 2.0.0-1 → 2.0.1-1
• ros-humble-mola: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-bridge-ros2: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-bridge-ros2-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-demos: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-imu-preintegration: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-imu-preintegration-dbgsym: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-input-euroc-dataset: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-euroc-dataset-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-kitti-dataset: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-kitti-dataset-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-kitti360-dataset: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-kitti360-dataset-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-mulran-dataset: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-mulran-dataset-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-paris-luco-dataset: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-rawlog: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-rawlog-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-rosbag2: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-input-rosbag2-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-kernel: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-kernel-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-launcher: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-launcher-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-lidar-odometry: 0.6.1-1 → 0.7.1-1
• ros-humble-mola-lidar-odometry-dbgsym: 0.6.1-1 → 0.7.1-1
• ros-humble-mola-metric-maps: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-metric-maps-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-msgs: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-msgs-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-pose-list: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-pose-list-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-relocalization: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-relocalization-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-state-estimation: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-state-estimation-simple: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-state-estimation-simple-dbgsym: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-state-estimation-smoother: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-state-estimation-smoother-dbgsym: 1.6.1-1 → 1.8.0-1
• ros-humble-mola-traj-tools: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-traj-tools-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-viz: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-viz-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-yaml: 1.6.0-1 → 1.6.3-1
• ros-humble-mola-yaml-dbgsym: 1.6.0-1 → 1.6.3-1
• ros-humble-mp2p-icp: 1.6.5-1 → 1.6.6-1
• ros-humble-mp2p-icp-dbgsym: 1.6.5-1 → 1.6.6-1
• ros-humble-nav-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-nav-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-novatel-oem7-driver: 20.6.0-1 → 20.7.0-1
• ros-humble-novatel-oem7-driver-dbgsym: 20.6.0-1 → 20.7.0-1
• ros-humble-novatel-oem7-msgs: 20.6.0-1 → 20.7.0-1
• ros-humble-novatel-oem7-msgs-dbgsym: 20.6.0-1 → 20.7.0-1
• ros-humble-omni-base-2dnav: 2.4.0-1 → 2.12.1-1
• ros-humble-omni-base-bringup: 2.4.1-1 → 2.9.0-1
• ros-humble-omni-base-controller-configuration: 2.4.1-1 → 2.9.0-1
• ros-humble-omni-base-description: 2.4.1-1 → 2.9.0-1
• ros-humble-omni-base-gazebo: 2.2.0-1 → 2.4.0-1
• ros-humble-omni-base-laser-sensors: 2.4.0-1 → 2.12.1-1
• ros-humble-omni-base-navigation: 2.4.0-1 → 2.12.1-1
• ros-humble-omni-base-rgbd-sensors: 2.4.0-1 → 2.12.1-1
• ros-humble-omni-base-robot: 2.4.1-1 → 2.9.0-1
• ros-humble-omni-base-simulation: 2.2.0-1 → 2.4.0-1
• ros-humble-openeb-vendor: 2.0.1-1 → 2.0.2-2
• ros-humble-openeb-vendor-dbgsym: 2.0.1-1 → 2.0.2-2
• ros-humble-osrf-pycommon: 2.1.4-1 → 2.1.6-1
• ros-humble-pal-gripper: 3.4.0-1 → 3.5.0-1
• ros-humble-pal-gripper-controller-configuration: 3.4.0-1 → 3.5.0-1
• ros-humble-pal-gripper-description: 3.4.0-1 → 3.5.0-1
• ros-humble-pal-gripper-simulation: 3.4.0-1 → 3.5.0-1
• ros-humble-pid-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-pid-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-pinocchio: 3.3.0-1 → 3.4.0-2
• ros-humble-pinocchio-dbgsym: 3.3.0-1 → 3.4.0-2
• ros-humble-play-motion2: 1.3.0-1 → 1.5.1-1
• ros-humble-play-motion2-dbgsym: 1.3.0-1 → 1.5.1-1
• ros-humble-play-motion2-msgs: 1.3.0-1 → 1.5.1-1
• ros-humble-play-motion2-msgs-dbgsym: 1.3.0-1 → 1.5.1-1
• ros-humble-pmb2-2dnav: 4.5.0-1 → 4.11.0-1
• ros-humble-pmb2-bringup: 5.4.0-1 → 5.7.0-1
• ros-humble-pmb2-controller-configuration: 5.4.0-1 → 5.7.0-1
• ros-humble-pmb2-description: 5.4.0-1 → 5.7.0-1
• ros-humble-pmb2-gazebo: 4.1.0-1 → 4.3.0-1
• ros-humble-pmb2-laser-sensors: 4.5.0-1 → 4.11.0-1
• ros-humble-pmb2-navigation: 4.5.0-1 → 4.11.0-1
• ros-humble-pmb2-robot: 5.4.0-1 → 5.7.0-1
• ros-humble-pmb2-simulation: 4.1.0-1 → 4.3.0-1
• ros-humble-pose-broadcaster: 2.41.0-1 → 2.43.0-1
• ros-humble-pose-broadcaster-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-position-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-position-controllers-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-qt-dotgraph: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui-app: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui-core: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui-cpp: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui-cpp-dbgsym: 2.2.3-2 → 2.2.4-1
• ros-humble-qt-gui-py-common: 2.2.3-2 → 2.2.4-1
• ros-humble-range-sensor-broadcaster: 2.41.0-1 → 2.43.0-1
• ros-humble-range-sensor-broadcaster-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-rclcpp: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-action: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-action-dbgsym: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-components: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-components-dbgsym: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-dbgsym: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-lifecycle: 16.0.11-1 → 16.0.12-1
• ros-humble-rclcpp-lifecycle-dbgsym: 16.0.11-1 → 16.0.12-1
• ros-humble-rclpy: 3.3.15-1 → 3.3.16-1
• ros-humble-rcpputils: 2.4.4-1 → 2.4.5-1
• ros-humble-rcpputils-dbgsym: 2.4.4-1 → 2.4.5-1
• ros-humble-realtime-tools: 2.11.0-1 → 2.12.0-1
• ros-humble-realtime-tools-dbgsym: 2.11.0-1 → 2.12.0-1
• ros-humble-resource-retriever: 3.1.2-1 → 3.1.3-1
• ros-humble-resource-retriever-dbgsym: 3.1.2-1 → 3.1.3-1
• ros-humble-ros2-control: 2.48.0-1 → 2.49.0-1
• ros-humble-ros2-control-test-assets: 2.48.0-1 → 2.49.0-1
• ros-humble-ros2-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-ros2-controllers-test-nodes: 2.41.0-1 → 2.43.0-1
• ros-humble-ros2action: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2bag: 0.15.13-1 → 0.15.14-1
• ros-humble-ros2cli: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2cli-test-interfaces: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2cli-test-interfaces-dbgsym: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2component: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2controlcli: 2.48.0-1 → 2.49.0-1
• ros-humble-ros2doctor: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2interface: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2launch: 0.19.8-1 → 0.19.9-1
• ros-humble-ros2lifecycle: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2lifecycle-test-fixtures: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2lifecycle-test-fixtures-dbgsym: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2multicast: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2node: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2param: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2pkg: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2run: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2service: 0.18.11-1 → 0.18.12-1
• ros-humble-ros2topic: 0.18.11-1 → 0.18.12-1
• ros-humble-rosbag2: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-compression: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-compression-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-compression-zstd: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-cpp: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-cpp-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-interfaces: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-interfaces-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-performance-benchmarking: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-py: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-default-plugins: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-mcap: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-mcap-testdata: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-test-common: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-tests: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-transport: 0.15.13-1 → 0.15.14-1
• ros-humble-rosbag2-transport-dbgsym: 0.15.13-1 → 0.15.14-1
• ros-humble-rqt-controller-manager: 2.48.0-1 → 2.49.0-1
• ros-humble-rqt-joint-trajectory-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-rqt-plot: 1.1.3-1 → 1.1.4-1
• ros-humble-rqt-robot-steering: 1.0.0-4 → 1.0.1-1
• ros-humble-rtabmap-conversions: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-conversions-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-demos: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-examples: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-launch: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-msgs: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-msgs-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-odom: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-odom-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-python: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-ros: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-rviz-plugins: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-rviz-plugins-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-slam: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-slam-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-sync: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-sync-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-util: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-util-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-viz: 0.21.9-1 → 0.21.10-1
• ros-humble-rtabmap-viz-dbgsym: 0.21.9-1 → 0.21.10-1
• ros-humble-sensor-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-sensor-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-sensor-msgs-py: 4.2.4-1 → 4.8.0-1
• ros-humble-septentrio-gnss-driver: 1.4.1-1 → 1.4.2-2
• ros-humble-septentrio-gnss-driver-dbgsym: 1.4.1-1 → 1.4.2-2
• ros-humble-shape-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-shape-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-shared-queues-vendor: 0.15.13-1 → 0.15.14-1
• ros-humble-simple-launch: 1.10.1-1 → 1.11.0-1
• ros-humble-sqlite3-vendor: 0.15.13-1 → 0.15.14-1
• ros-humble-sros2: 0.10.5-1 → 0.10.6-1
• ros-humble-sros2-cmake: 0.10.5-1 → 0.10.6-1
• ros-humble-std-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-std-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-std-srvs: 4.2.4-1 → 4.8.0-1
• ros-humble-std-srvs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-steering-controllers-library: 2.41.0-1 → 2.43.0-1
• ros-humble-steering-controllers-library-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-stereo-image-proc: 3.0.6-1 → 3.0.7-1
• ros-humble-stereo-image-proc-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-stereo-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-stereo-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-talos-moveit-config: 2.0.0-1 → 2.0.1-1
• ros-humble-tiago-2dnav: 4.5.0-1 → 4.9.0-1
• ros-humble-tiago-bringup: 4.7.1-1 → 4.14.0-1
• ros-humble-tiago-controller-configuration: 4.7.1-1 → 4.14.0-1
• ros-humble-tiago-description: 4.7.1-1 → 4.14.0-1
• ros-humble-tiago-laser-sensors: 4.5.0-1 → 4.9.0-1
• ros-humble-tiago-moveit-config: 3.1.1-1 → 3.1.2-1
• ros-humble-tiago-navigation: 4.5.0-1 → 4.9.0-1
• ros-humble-tiago-robot: 4.7.1-1 → 4.14.0-1
• ros-humble-tracetools-image-pipeline: 3.0.6-1 → 3.0.7-1
• ros-humble-tracetools-image-pipeline-dbgsym: 3.0.6-1 → 3.0.7-1
• ros-humble-trajectory-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-trajectory-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-transmission-interface: 2.48.0-1 → 2.49.0-1
• ros-humble-transmission-interface-dbgsym: 2.48.0-1 → 2.49.0-1
• ros-humble-tricycle-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-tricycle-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-tricycle-steering-controller: 2.41.0-1 → 2.43.0-1
• ros-humble-tricycle-steering-controller-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-turtlebot3: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-bringup: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-cartographer: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-description: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-example: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-msgs: 2.2.3-1 → 2.3.0-1
• ros-humble-turtlebot3-msgs-dbgsym: 2.2.3-1 → 2.3.0-1
• ros-humble-turtlebot3-navigation2: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-node: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-node-dbgsym: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot3-teleop: 2.1.5-1 → 2.2.5-1
• ros-humble-turtlebot4-ignition-bringup: 1.0.2-1 → 1.0.3-1
• ros-humble-turtlebot4-ignition-gui-plugins: 1.0.2-1 → 1.0.3-1
• ros-humble-turtlebot4-ignition-gui-plugins-dbgsym: 1.0.2-1 → 1.0.3-1
• ros-humble-turtlebot4-ignition-toolbox: 1.0.2-1 → 1.0.3-1
• ros-humble-turtlebot4-ignition-toolbox-dbgsym: 1.0.2-1 → 1.0.3-1
• ros-humble-turtlebot4-setup: 1.0.5-1 → 1.0.6-1
• ros-humble-turtlebot4-simulator: 1.0.2-1 → 1.0.3-1
• ros-humble-ur: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-bringup: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-calibration: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-calibration-dbgsym: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-client-library: 1.6.0-1 → 1.8.0-1
• ros-humble-ur-client-library-dbgsym: 1.6.0-1 → 1.8.0-1
• ros-humble-ur-controllers: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-controllers-dbgsym: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-dashboard-msgs: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-dashboard-msgs-dbgsym: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-description: 2.1.10-1 → 2.1.11-1
• ros-humble-ur-moveit-config: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-msgs: 2.1.0-1 → 2.2.0-1
• ros-humble-ur-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
• ros-humble-ur-robot-driver: 2.5.2-1 → 2.6.0-1
• ros-humble-ur-robot-driver-dbgsym: 2.5.2-1 → 2.6.0-1
• ros-humble-velocity-controllers: 2.41.0-1 → 2.43.0-1
• ros-humble-velocity-controllers-dbgsym: 2.41.0-1 → 2.43.0-1
• ros-humble-visualization-msgs: 4.2.4-1 → 4.8.0-1
• ros-humble-visualization-msgs-dbgsym: 4.2.4-1 → 4.8.0-1
• ros-humble-webots-ros2: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-control: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-control-dbgsym: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-driver: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-driver-dbgsym: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-epuck: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-importer: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-mavic: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-msgs: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-msgs-dbgsym: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-tesla: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-tests: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-tiago: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-turtlebot: 2023.1.3-1 → 2025.0.0-2
• ros-humble-webots-ros2-universal-robot: 2023.1.3-1 → 2025.0.0-2
• ros-humble-wireless-msgs: 1.1.2-1 → 1.1.3-1
• ros-humble-wireless-msgs-dbgsym: 1.1.2-1 → 1.1.3-1
• ros-humble-wireless-watcher: 1.1.2-1 → 1.1.3-1
• ros-humble-wireless-watcher-dbgsym: 1.1.2-1 → 1.1.3-1
• ros-humble-xacro: 2.0.8-1 → 2.0.13-1
• ros-humble-zed-msgs: 4.2.2-1 → 4.2.5-1
• ros-humble-zed-msgs-dbgsym: 4.2.2-1 → 4.2.5-1
• ros-humble-zstd-vendor: 0.15.13-1 → 0.15.14-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:

• Abed Al Rahman Al Mrad
• Adam Serafin
• Aditya Pande
• Aina Irisarri
• Alejandro Hernandez Cordero
• Alex Moriarty
• Andrea Capodacqua
• Antonio Brandi
• Apex AI, Inc.
• Automatika Robotics
• Bence Magyar
• Bernd Pfrommer
• Chris Lalancette
• Cyberbotics
• Davide Costa
• Dirk Thomas
• Dorian Scholz
• Elevate Robotics
• Ethan Gao
• Felix Exner
• Foxglove
• G.A. vd. Hoorn
• Geoffrey Biggs
• Husarion
• Ivan Paunovic
• Jean-Pierre Busch
• Jordan Palacios
• Jordi Pages
• Jose Luis Blanco-Claraco
• Jose Mastrangelo
• Joseph Mirabel
• Justin Carpentier
• Kevin Hallenbeck
• Kimberly McGuire (Bitcraze AB)
• Luca Marchionni
• Luis Camero
• Mabel Zhang
• Mamoru Sobue
• Marq Rasmussen
• Mathieu Labbe
• Max Krogius
• Michael Jeronimo
• Michael Orlov
• Micho Radovnikovich
• Noel Jimenez
• NovAtel Support
• Olivier Kermorgant
• Pyo
• ROS Security Working Group
• Robert Haschke
• Roni Kreinin
• Ryohsuke Mitsudome
• STEREOLABS
• Shane Loretz
• TIAGo PAL support team
• TIAGo support team
• Tibor Dome
• Tony Baltovski
• Vincent Rabaud
• Víctor Mayoral-Vilches
• William Woodall
• Yue Erro
• mitsudome-r
• rkreinin

1 post - 1 participant

Read full topic

The next meeting for the Cloud Robotics Working Group will be at 2025-04-07T17:00:00Z UTC→2025-04-07T18:00:00Z UTC, where we will discuss uploading robot data to the cloud. We plan to cover the possible benefits and drawbacks of uploading data, how we have seen data upload being done, and the kind of data that is best uploaded.

Last meeting, the group had a shorter meeting and discussed LLMs in robotics and software development, and the new format of meeting with discussion topics being proposed. If you would like to see the meeting, the recording is available on YouTube. If you would like to propose a topic you are interested in discussing with the group, please add a comment on the Github Issue.

We are still looking for guest speakers for cloud robotics. If you would be willing to give a talk, 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 or keep an eye on the Cloud Robotics Hub.

Hopefully we will see you there!

3 posts - 2 participants

Read full topic

Hello everyone!

We’re happy to announce 13 new package and 188 updates are now available in ROS 2 Rolling Ridley

This sync was tagged as rolling/2025-03-28 .

Package Updates for rolling

Added Packages [13]:

• ros-rolling-ament-cmake-ros-core: 0.14.0-1
• ros-rolling-dynamixel-hardware-interface: 1.4.0-1
• ros-rolling-dynamixel-hardware-interface-dbgsym: 1.4.0-1
• ros-rolling-kinova-gen3-6dof-robotiq-2f-85-moveit-config: 0.2.2-2
• ros-rolling-kinova-gen3-7dof-robotiq-2f-85-moveit-config: 0.2.2-2
• ros-rolling-kortex-description: 0.2.2-2
• ros-rolling-picknik-reset-fault-controller: 0.0.4-2
• ros-rolling-picknik-reset-fault-controller-dbgsym: 0.0.4-2
• ros-rolling-picknik-twist-controller: 0.0.4-2
• ros-rolling-picknik-twist-controller-dbgsym: 0.0.4-2
• ros-rolling-ros2-control-cmake: 0.1.1-1
• ros-rolling-zed-msgs: 4.2.5-1
• ros-rolling-zed-msgs-dbgsym: 4.2.5-1

Updated Packages [188]:

• ros-rolling-ackermann-steering-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-ackermann-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-actionlib-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-actionlib-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-admittance-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-admittance-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-ament-cmake-ros: 0.13.1-1 → 0.14.0-1
• ros-rolling-autoware-cmake: 1.0.0-1 → 1.0.1-1
• ros-rolling-autoware-lint-common: 1.0.0-1 → 1.0.1-1
• ros-rolling-bicycle-steering-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-bicycle-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-common-interfaces: 5.4.2-1 → 5.5.0-1
• ros-rolling-diagnostic-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-diagnostic-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-diff-drive-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-diff-drive-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-domain-coordinator: 0.13.1-1 → 0.14.0-1
• ros-rolling-dynamixel-sdk: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-sdk-custom-interfaces: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-sdk-custom-interfaces-dbgsym: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-sdk-dbgsym: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-sdk-examples: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-sdk-examples-dbgsym: 3.8.1-1 → 3.8.2-1
• ros-rolling-dynamixel-workbench: 2.2.3-4 → 2.2.4-1
• ros-rolling-dynamixel-workbench-toolbox: 2.2.3-4 → 2.2.4-1
• ros-rolling-dynamixel-workbench-toolbox-dbgsym: 2.2.3-4 → 2.2.4-1
• ros-rolling-effort-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-effort-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-ffmpeg-encoder-decoder: 1.0.1-1 → 2.0.0-1
• ros-rolling-ffmpeg-encoder-decoder-dbgsym: 1.0.1-1 → 2.0.0-1
• ros-rolling-ffmpeg-image-transport: 1.0.2-1 → 2.0.1-1
• ros-rolling-ffmpeg-image-transport-dbgsym: 1.0.2-1 → 2.0.1-1
• ros-rolling-ffmpeg-image-transport-tools: 1.0.1-1 → 2.1.1-1
• ros-rolling-ffmpeg-image-transport-tools-dbgsym: 1.0.1-1 → 2.1.1-1
• ros-rolling-force-torque-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
• ros-rolling-force-torque-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-forward-command-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-forward-command-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-geometry-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-geometry-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-gpio-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-gpio-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-gripper-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-gripper-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-hls-lfcd-lds-driver: 2.0.4-5 → 2.1.0-1
• ros-rolling-hls-lfcd-lds-driver-dbgsym: 2.0.4-5 → 2.1.0-1
• ros-rolling-imu-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
• ros-rolling-imu-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-joint-state-broadcaster: 4.21.0-1 → 4.22.0-1
• ros-rolling-joint-state-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-joint-trajectory-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-joint-trajectory-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-kitti-metrics-eval: 1.6.2-1 → 1.6.3-1
• ros-rolling-kitti-metrics-eval-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mecanum-drive-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-mecanum-drive-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-mola: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-bridge-ros2: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-bridge-ros2-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-demos: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-imu-preintegration: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-imu-preintegration-dbgsym: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-input-euroc-dataset: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-euroc-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-kitti-dataset: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-kitti-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-kitti360-dataset: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-kitti360-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-mulran-dataset: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-mulran-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-paris-luco-dataset: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-paris-luco-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-rawlog: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-rawlog-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-rosbag2: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-input-rosbag2-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-kernel: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-kernel-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-launcher: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-launcher-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-lidar-odometry: 0.7.0-1 → 0.7.1-1
• ros-rolling-mola-lidar-odometry-dbgsym: 0.7.0-1 → 0.7.1-1
• ros-rolling-mola-metric-maps: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-metric-maps-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-msgs: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-msgs-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-pose-list: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-pose-list-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-relocalization: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-relocalization-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-state-estimation: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-state-estimation-simple: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-state-estimation-simple-dbgsym: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-state-estimation-smoother: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-state-estimation-smoother-dbgsym: 1.7.0-1 → 1.8.0-1
• ros-rolling-mola-traj-tools: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-traj-tools-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-viz: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-viz-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-yaml: 1.6.2-1 → 1.6.3-1
• ros-rolling-mola-yaml-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-rolling-nav-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-nav-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-parallel-gripper-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-parallel-gripper-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-pid-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-pid-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-pose-broadcaster: 4.21.0-1 → 4.22.0-1
• ros-rolling-pose-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-position-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-position-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-range-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
• ros-rolling-range-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-rmw-desert: 2.0.0-1 → 3.0.0-1
• ros-rolling-rmw-desert-dbgsym: 2.0.0-1 → 3.0.0-1
• ros-rolling-rmw-zenoh-cpp: 0.4.0-1 → 0.5.0-1
• ros-rolling-rmw-zenoh-cpp-dbgsym: 0.4.0-1 → 0.5.0-1
• ros-rolling-robot-localization: 3.9.1-1 → 3.9.2-2
• ros-rolling-robot-localization-dbgsym: 3.9.1-1 → 3.9.2-2
• ros-rolling-ros-gz: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-bridge: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-bridge-dbgsym: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-image: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-image-dbgsym: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-interfaces: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-interfaces-dbgsym: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-sim: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-sim-dbgsym: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros-gz-sim-demos: 2.1.5-1 → 2.1.6-1
• ros-rolling-ros2-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-ros2-controllers-test-nodes: 4.21.0-1 → 4.22.0-1
• ros-rolling-rqt-joint-trajectory-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-rqt-robot-steering: 1.0.0-5 → 1.0.1-2
• ros-rolling-rviz-assimp-vendor: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-common: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-common-dbgsym: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-default-plugins: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-default-plugins-dbgsym: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-ogre-vendor: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-ogre-vendor-dbgsym: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-rendering: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-rendering-dbgsym: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-rendering-tests: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz-visual-testing-framework: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz2: 14.4.2-1 → 14.4.4-1
• ros-rolling-rviz2-dbgsym: 14.4.2-1 → 14.4.4-1
• ros-rolling-sensor-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-sensor-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-sensor-msgs-py: 5.4.2-1 → 5.5.0-1
• ros-rolling-shape-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-shape-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-std-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-std-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-std-srvs: 5.4.2-1 → 5.5.0-1
• ros-rolling-std-srvs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-steering-controllers-library: 4.21.0-1 → 4.22.0-1
• ros-rolling-steering-controllers-library-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-stereo-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-stereo-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-test-ros-gz-bridge: 2.1.5-1 → 2.1.6-1
• ros-rolling-trajectory-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-trajectory-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-tricycle-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-tricycle-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-tricycle-steering-controller: 4.21.0-1 → 4.22.0-1
• ros-rolling-tricycle-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-ur: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-calibration: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-calibration-dbgsym: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-client-library: 1.7.1-1 → 1.8.0-1
• ros-rolling-ur-client-library-dbgsym: 1.7.1-1 → 1.8.0-1
• ros-rolling-ur-controllers: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-controllers-dbgsym: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-dashboard-msgs: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-dashboard-msgs-dbgsym: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-description: 3.0.1-1 → 3.0.2-1
• ros-rolling-ur-moveit-config: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-msgs: 2.1.0-1 → 2.2.0-1
• ros-rolling-ur-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
• ros-rolling-ur-robot-driver: 3.1.0-1 → 3.1.1-1
• ros-rolling-ur-robot-driver-dbgsym: 3.1.0-1 → 3.1.1-1
• ros-rolling-velocity-controllers: 4.21.0-1 → 4.22.0-1
• ros-rolling-velocity-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
• ros-rolling-visualization-msgs: 5.4.2-1 → 5.5.0-1
• ros-rolling-visualization-msgs-dbgsym: 5.4.2-1 → 5.5.0-1
• ros-rolling-xacro: 2.0.12-1 → 2.0.13-1
• ros-rolling-zenoh-cpp-vendor: 0.4.0-1 → 0.5.0-1
• ros-rolling-zenoh-cpp-vendor-dbgsym: 0.4.0-1 → 0.5.0-1

Removed Packages [1]:

• ros-rolling-velodyne-description

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:

• Aditya Pande
• Alejandro Hernandez
• Alejandro Hernandez Cordero
• Alex Moriarty
• Anthony Baker
• Bence Magyar
• Bernd Pfrommer
• Brandon Ong
• Davide Costa
• Dirk Thomas
• Felix Exner
• G.A. vd. Hoorn
• Jose Luis Blanco-Claraco
• Jose-Luis Blanco-Claraco
• Pyo
• Robert Haschke
• Ryohsuke Mitsudome
• STEREOLABS
• Tom Moore
• Tully Foote
• Yadunund
• lovro

1 post - 1 participant

Read full topic

ROS News for the Week of March 24th, 2025

The website for ROSCon 2025 in the Republic of Singapore is now live.

Three big things to know:

• The CFP is open! Send us your talks!
• We are looking for event sponsors.
• The ROSCon Diversity Scholarship program is now open!

Scholarship details are available here and applications are due 2025-04-18T07:00:00Z UTC.

Our colleagues over at JAXA have released the source code for the their robot on the international space station. – ROS / Gazebo source code – also available for Isaac Sim.

Check out this amazing 3D printed ROS 2 omnidirectional robot – source code.

It was the European Robotics Forum this week. OSRA members Intrinsic, Bosch, Huawei, Husarion and ROS-I were major supporters. Our colleagues in the area also organized a ROS meetup (pictured above).

Events

• 2025-03-31 ROS OpenEmbedded Community Group
• 2025-04-11 Mistral AI Robotics Hackathon Paris
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
• 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
• 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
• 2025-05-24 ROS MeetUp in Cali, Colombia!
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
• 2025-09-09 ROSCon JP in Nagoya
• 2025-10-27 =>2025-10-30 ROSCon Singapore
• 2025-11-17 => 2025-11-20 Joint ROSCon Germany and France

News

• Announcing ROSCon 2025 in the Republic of Singapore
• OSRF Google Summer of Code 2025
• Ros-controls PMC meeting 26th March 2025
• ROS PMC Minutes for March 25, 2025
• Ubuntu now officially supports NVIDIA Jetson: powering the future of AI at the edge
• ICRA 2025: CALL FOR STARTUPS
• ICRA 2025: Call for Late Breaking Results
• Introducing RDA: Revolutionizing ROS Data Management for Robotics Teams
• Torc debuts physical AI for long-haul trucking at NVIDIA GTC 2025
• Zoox issues voluntary software recall for 258 vehicles
• Contoro picks up $12M to scale container unloading robots
• BlueHalo wins $30M follow-on contract with the U.S. Navy
• PIXKIT: A Drive-by-Wire Chassis Platform for Autonomous Vehicle R&D
• Discover 3D-Printed Robots and More on Video Friday

ROS

• Introducing rosidlcpp: Building interface packages 10x faster
• Faster rclpy executor now in Rolling
• New Issue Template Added for ROS 2 Documentation
• ROS 2 Android Sensor Bridge
• Inspect, compare and align multiple grid maps in an intuitive & fast GUI
• JAXA: Int-Ball2 ROS / Gazebo Simulator Released – Int-Ball2 Simulator (Isaac Sim)
• Video: Making an omnidirectional ROS 2 robot
• QOI (Quite OK Image) format available as image_transport (lossless RGB(A) 50x faster than PNG)
• Challenges with ROS 2 on commercial robots
• Should all released packages be documented by ROS infrastructure?
• ROS Virtual Reality (VR) Interface
• Upcoming switch of Windows installation to pixi/conda
• ROS 2 platform based program designed to control and Monitor ATVs.
• Video: Event Cameras: a New Way of Sensing - Davide Scaramuzza - ICCP 2024 Keynote
• Video: Gazebo Community Meeting - 2025-03-26 - Benjamin Perseghetti: Testing Hardware Performance with Gazebo
• OpenMANIPULATOR-X Now Supports ROS 2 Jazzy & Gazebo Harmonic!
• MTConnect OPC UA Bridge
• An autonomous vehicle stack, including perception, planning, and control, built for CARLA.
• PickNik Robotics ROS Support Library
• A curated list of awesome robot descriptions (URDF, MJCF) - See also: Gazebo Fuel
• A GUI Tool for Monitoring ROS 2 Topic Availability
• A Fleet of Unitree GOs (GO1 and GO2) capable of Heterogeneous Collaborative Exploration. - details
• MegaRover Source Code
• manymove: plan and execute moves with manipulators in ROS2
• Under water SLAM
• Tier4 ROS Bag Extensions
• NVIDIA-Omniverse/PhysX ChangeLog
• Dual dexterous hand manipulation tasks through Isaac Gym

Have a Minute ?

It would be really awesome if someone from the community could fix this autocomplete issue with ros2 topic pub before the Kilted feature freeze.

We would also appreciate some help with the official ros_gz documentation.

Please just assign yourself the ticket and go to town!

1 post - 1 participant

Read full topic

I’m announcing a new executor that’s now available for rclpy in Rolling, which is a port of the rclcpp EventsExecutor approach for use in Python. This was motivated by the large increase in CPU usage my company (Merlin Labs) experienced when porting an existing project from Noetic to Iron, most especially among our Python-based nodes. More background and benchmarks are available here, but the upshot is CPU usage has been observed to be as little as a tenth of that of the default SingleThreadedExecutor for some workloads!

Functionally, it should largely be a drop-in replacement substituting rclpy.experimental.EventsExecutor for rclpy.executors.SingleThreadedExecutor in your code. Being single threaded, it does functionally ignore all callback groups and treat every event as mutually exclusive in its current form. Additionally, it may start to get inefficient if you have a large number of ROS timers running in the same process.

This feature is expected to be part of the upcoming Kilted release, and there is also an effort underway to backport it to Jazzy.

3 posts - 3 participants

Read full topic

Hello ROS people,

Has anyone successfully used floating joints with MoveIt 2?

I’m trying to describe a UAV in URDF format to leverage MoveIt 2’s libraries for planning.I am mostly concerned with 3D translation, not orientation.

In theory, a floating joint + position_only_ik:True would do the trick. However, in practice, I can’t get the Joint State Publisher to recognize the joint, even though MoveIt 2’s documentation claims support for floating joints.

While I understand that other methods may be simpler for UAV planning and that the purpose of Moveit2 and URDF is not to plan for UAVs, I want to explore whether something like this is possible. I find it hard to believe that the best solution would be to stack three prismatic joints with intermediate links to achieve 3D translation.

4 posts - 4 participants

Read full topic

Hello Community!

We, the ros2_control PMC, would like to open this discussion to propose an extension to the JointLimits struct in URDF XML and gather community feedback.

ROS 2 is designed to integrate seamlessly with industrial manipulators, service robots, and other robotic ecosystems. While the existing position and velocity limits cover basic use cases, more advanced motion planning and task execution require additional constraints. Specifically, acceleration and jerk limits play a crucial role in ensuring smooth, safe, and precise motion. The proposed PRs introduce these additional limits into the URDF specification, enhancing motion control capabilities:

• Extend parsing of acceleration, deceleration and jerk limits from `limit` tag by saikishor · Pull Request #212 · ros/urdfdom · GitHub
• Extend JointLimits class to include acceleration, deceleration and jerk limits by saikishor · Pull Request #83 · ros/urdfdom_headers · GitHub

Once these changes are merged, the next step would be integrating these extended joint limits into the ros2_control ecosystem. This would allow controllers to automatically enforce these constraints, ensuring safer and more precise command execution—without requiring users to manually implement workarounds to respect hardware limits.

We’d love to hear the community’s thoughts on this proposal. Do you see value in adding acceleration and jerk limits to URDF? Are there any potential challenges or alternative approaches we should consider?

A related discussion can be found here: Allow for More Complex Joints in URDF

Looking forward to your feedback!

3 posts - 2 participants

Read full topic

ROS maintains package-level indexing and documentation with rosindex and rosdoc2 for repos that have entries in rosdistro. There are a variety of reasons why a package in rosdistro might not have their documentation appear, but one reason is because the author did not specify a source or doc repo in their release to rosdistro.

Are there any package authors that for some reason want to have their package released in ROS 2 but not appear in rosindex or rosdoc2?

Presently, rosindex attempts to document packages with no doc or source repo by diving into the release tracks, while rosdoc2 shows nothing. So a package like, e.g. radar_msgs has an entry in rosindex, but not in rosdoc2.

My inclination is to assume that the non-documentation status of these packages is inadvertent rather than deliberate, so I would be inclined to correct the ‘mistake’ by looking into the release entries in rosdistro, and presenting that as the source for documentation This is what rosindex does currently, but not rosdoc2.

Any thoughts on this?

Here is a list of packages with release entries but no doc or source, hence not appearing in rosdoc2:

clearpath_mecanum_drive_controller
ifm3d_core
libg2o
marvelmind_ros2_msgs
nonpersistent_voxel_layer
ompl
ortools_vendor
picknik_ament_copyright
radar_msgs
ros_industrial_cmake_boilerplate
topic_based_ros2_control
gazebo_ros_pkgs

6 posts - 4 participants

Read full topic

I would like to get in touch with companies and organizations that use ROS2 on commercial robots or that are developing with ROS2 for commercial robots. I am especially interested in issues that robot developers currently face when bringing a robot to market. Topics could be difficulties with (fast) system bring-up, graceful degradation, use of lifecycle nodes, heartbeats, DDS, debugging and analyzing nodes, hard real-time requirements, communication with other industrial platforms, updating systems in the field, etc. My goal is to identify common challenges that multiple parties encounter and that we potentially could address in applied research projects.

12 posts - 11 participants

Read full topic

Hi ROS Developers,

To improve the process of reporting and tracking issues related to the ROS 2 documentation, we have introduced a new issue template!

This update has been merged in add github issue template. by fujitatomoya · Pull Request #5140 · ros2/ros2_documentation · GitHub and is now online.
The new template provides a structured format for reporting documentation issues, making it easier for contributors to provide relevant details and for maintainers to address them efficiently.

We encourage all contributors to use this template when submitting documentation-related issues to help streamline discussions and improvements. Your feedback is always welcome—let us know if you have any suggestions!

Happy documenting!

@tomoyafujita
@Katherine_Scott
@christophebedard

1 post - 1 participant

Read full topic

Announcing ROSCon 2025 in the Republic of Singapore

Our call for proposals and diversity scholarship application form are now open and we are currently seeking sponsors for ROSCon 2025!

ROSCon 2025

I am happy to announce that we just launched the ROSCon 2025 website! This year’s ROSCon will take place in the Republic of Singapore 2025-10-27T07:00:00Z UTC→2025-10-29T07:00:00Z UTC.

The Republic of Singapore has a long history of supporting the ROS project and the robotics industry and we’re excited for our Singaporean colleagues to show us what they have been working on! Singapore is home to a number of ROS core contributors, most of the Open-RMF core contributors, our colleagues at ROS Industrial AP and OSRA member organization National Robotics Program of Singapore.

If you’re a ROS developer you won’t want to miss ROSCon 2025; we’ll have most of the ROS core developers and contributors all in one place for three days for talks, workshops, birds-of-a-feather sessions, robot demonstrations, and vendor exhibitions. Last year ROSCon completely sold out, so we recommend you keep an eye on the website and plan to register early.

Sponsor ROSCon 2025

We can’t make ROSCon happen without the generous support of our sponsors. If your organization would like to exhibit at ROSCon you can find our sponsorship prospectus here. We offer five different levels of event sponsorship along with a variety of sponsorship add-ons to increase your exposure. Perhaps you would like to help support one of our many ROSCon Diversity Scholars? Whatever your interests, we encourage you to book your space early, as exhibit space out last year and fully expect it to sell out again this year.

ROSCon Call for Proposals & Important Dates

I am happy to announce that ROSCon CFP opens today, March 24th! We want to encourage everyone in the ROS community to submit their talk and workshop proposals, don’t hold back! We absolutely want to hear about your ROS development experiences. The advice I give to all my interns and employees is to never self-censor, let the CFP reviewers decide if your idea is worth presenting. If you’ve never attended a ROSCon we absolutely want to hear what you have to say!

ROSCon workshop proposals are due 2025-05-05T07:00:00Z UTC and regular session talk proposals are due 2025-06-02T07:00:00Z UTC, about a month later. We plan on having proposals reviewed and finalized by 2025-07-07T07:00:00Z UTC. All of the important event dates are listed below and on the ROSCon website.

• Call for Proposals circulated
  • 2025-03-24T07:00:00Z UTC
• Diversity Scholarship application deadline
  • 2025-04-18T07:00:00Z UTC
• Workshop submission deadline
  • 2025-05-05T07:00:00Z UTC
• Proposal submission deadline
  • 2025-06-02T07:00:00Z UTC
• Proposal acceptance notification
  • 2025-07-14T07:00:00Z UTC
• Ticket Sales Begin
  • 2025-06-16T07:00:00Z UTC
• Early registration deadline
  • 2025-08-22T07:00:00Z UTC
• Late registration starts
  • 2025-10-06T07:00:00Z UTC

ROSCon 2025 Diversity Scholarships

The ROSCon Diversity Scholarship is the only program we offer to help students and new open source contributors attend ROSCon. If you would like to attend ROSCon 2025 but don’t have the financial means, this is our one and only program to help you get there! The scholarship covers ROSCon admission, travel, and shared lodging at the event. We recommend you start your application early! Like last year, this year’s ROSCon diversity scholarship application form is currently open and accepting applications. This year the application deadline for Diversity Scholarships will be 2025-04-18T07:00:00Z UTC, a little less than a month from now.

5 posts - 2 participants

Read full topic

Today I’ve learned about QOI (Quite OK Image) format (while reading GIMP 3.0 release notes!). I followed the urge and implemented image_transport for it.

It can be used for lossless compression of RGB or RGBA images. Its compression ratio is comparable to lossless PNG, but encoding is 10-50x faster and decoding 2-4x faster. Check the benchmark.

Thanks to our package image_transport_codecs, qoi_image_transport offers not only the normal image_transport functionality (on subtopic “qoi”), but it also provides a pure C++/Python interface to do image encoding and decoding without the need of going through the tedious and unreliable pub/sub cycle. If you’re interested, I’m curious about your opinions on image_transport_codecs and whether such thing should be used as the general backend for image_transport.

Slightly related advertisement:

If you now want to convert some of your bag files and images in them to QOI format, you can utilize our cras_bag_tools/filter_bag utility, e.g. with a recompress config. But feel free to explore also the other implemented filters, e.g. for topic filtering by name/type/size, TF filtering, remapping of topics or fixing wrong frame_ids .

Even less relevant advertisement:

The package is fully REUSE-compatible. This means automated license checking and composition of SBOM is possible. Join the movement and upgrade your packages with REUSE! There is even a handy Github Action for verifying compatibility.

2 posts - 1 participant

Read full topic

ROS News for the Week of March 17th, 2025

Thanks to some design contributions from our friends at HeloRobo.com the landing page on docs.ros.org just got a facelift!

The OSRA turned one year old this week! As of this week we have 48 corporate members, five open source projects, and close to 200 individual members.

The week we launched our 2025 OSRF Google Summer of Code program. JdeRobot is also looking for GSoC students. We’ve also opened up our 2025 Internship open thread. where companies can post their internship opportunities.

We had some greatnews out of NVIDIA GTC: Jetson boards will finally run recent Ubuntu releases! No more using Docker containers to run Jazzy on your Jetson!

Introducing "maps“: Inspect, compare and align multiple grid maps

Our first ever ROS meetup in Colombia will happen May 24th in Cali!

Events

• 2025-03-22 Seeed Embodied AI Hackathon with LeRobot
• 2025-03-24 ROS Meetup at European Robotics Forum
• 2025-03-24 Intrinsic / Automatica Sponsored Fun Run at European Robotics Forum
• 2025-03-25 Space ROS Club Japan
• 2025-03-26 Dronecode Philly Meetup
• 2025-04-11 Mistral AI Robotics Hackathon Paris
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
• 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
• 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
• 2025-05-24 ROS MeetUp in Cali, Colombia!
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
• 2025-09-09 ROSCon JP in Nagoya
• 2025-10-27 =>2025-10-30 ROSCon Singapore
• 2025-11-17 => 2025-11-20 Joint ROSCon Germany and France

News

• 2025 Internship Open Thread
• OSRF Google Summer of Code 2025
• Participate in GSoC 2025 with JdeRobot open-source organization
• Joint ROSCon FR + DE 2025
• Harvard Business School: “We find that firms would need to spend 3.5 times more on software than they currently do if OSS did not exist.”
• Ubiquity Robotics has joined the OSRA!
• Rerun.io Raises $17M Series A - TechCrunch
• Video OpenMV’s Kwabena Agyeman - OpenCV In Conversation Ep. 001
• Weekly Robotics #304
• Raising the Bar: Adding Height and Versatility to Mobile Manipulator Robots
• Accepted Talks: at Robotics Science and Systems
• CFP: Agents-In-Interactions CVPR Workshop
• Tera AI comes out of stealth with $7.8M to provide visual navigation for robots
• Intrinsic and NVIDIA deepen platform integrations for intelligent robotics
• Nvidia debuts Groot N1, a foundation model for humanoid robotics
• Discover Superhumanoid Robots on Video Friday
• Salto Robot Masters Squirrel-Like Branch Leaping
• Biggest robotics news from NVIDIA GTC day 2
• Locus Array automates induction, storage for ‘zero touch’ fulfillment
• Dexterity launches Mech dual-armed mobile manipulator for truck loading
• Anyware Robotics picks up $12M seed funding to automate container unloading
• Yaak adds Vehicle Data to Hugging Face – The Data

ROS

• docs.ros.org just got a facelift!
• Introducing "maps“: Inspect, compare and align multiple grid maps
• Best news out of NVIDIA GTC: Jetsons Finally Run Recent Ubuntu Releases
• Noetic EOL plan
• ROS Noetic is reaching End of Life in May 2025 – Which additional packages do you need in ROS Noetic ESM?
• New Packages for Noetic 2025-03-20
• Running ROS Noetic in Docker: A Practical Guide for Simulation and Teleoperation
• Dynamic URDF files/robot descriptions
• Aerial Robotics Meeting - March 20th 2025
• Declarative ROS presentation slides & the Robograph project kickoff
• Why is there no ament_python_simple?
• Reusable Components in URDF
• Robotiq Hand-E gripper ROS 2 Humble driver
• Clearpath’s ROS 2 driver for the Ewellix lift columns.
• New TurtleBot3 AutoRace Tutorial Examples Released!
• Official ROS 2 Driver Release for Mitsubishi Electric Industrial Robot MELFA
• Nav2 Migrated to TwistStamped to replace Twist for cmd_vel Topics
• Notice: tj-actions/changed-files 3rd party GitHub Action compromised
• ManyMove – C++/Python Behavior Trees for Robot Manipulators
• ROS 2 Jazzy Packages for Ubuntu 22.04
• FloPE: Flower Pose Estimation for Precision Pollination
• MASt3R-SLAM: Real-Time Dense SLAM with 3D Reconstruction Priors
• NASA: A stream-based runtime-verification framework for generating hard real-time C code.
• Running Ignition Gazebo Ionic on Google Colab
• Video Revolution from ROS 1 to ROS 2
• OpenManipulator for controlling in Gazebo and Moveit with ROS
• Pixi Release 0.43.0 - 2025-03-20
• KiCad Version 9.0.1 Release Candidate 1
• SpatialLM-Llama-1B on Hugging Face
• Open Source Modern Robotics Course Wiki
• CVPR 2025: MAGiC-SLAM: Multi-Agent Gaussian Globally Consistent SLAM
• Setting Up LeRobot Using API Standalone Method in NVIDIA Isaac Sim
• OpenBot-Waffle Robot
• Mevius: Roll Your Own Quadruped
• Open_Duck_Mini: Clone BDX droid

Got a Minute

Why not send us a pull request?

We need someone to help unify the ROS_GZ bridge documentation and another person to fix the documentation for Gazebo plugins. If you are looking for something more technical, why not fix this broken type error exception in Gazebo?

1 post - 1 participant

Read full topic

Hey everyone,

I’m currently diving into learning and working with ROS (Robot Operating System) for my robotics projects, and I’m considering using Windows Subsystem for Linux (WSL) as my primary development environment. From what I’ve read, WSL is a great option to run Linux tools directly on Windows without the need for dual-booting or setting up a VM, but I’m wondering if it’s fully sufficient for all aspects of ROS development.

Has anyone used WSL for ROS before? Specifically, I’m curious to know if it can handle all the required dependencies, the ROS graphical tools, and simulations like Gazebo or RViz, and whether there are any limitations that might come up. Also, is it good for working with robots like Baxter or other hardware interfaces that might require low-latency communication or more complex setups?

Any tips or experiences you can share would be really helpful!

Thanks in advance!

9 posts - 7 participants

Read full topic

We’re happy to announce 0 new packages and 19 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-03-20.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [19]:

• ros-noetic-costmap-cspace: 0.17.5-1 → 0.17.6-1
• ros-noetic-depthai-bridge: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-descriptions: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-examples: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-filters: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros-driver: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros-msgs: 2.11.0-1 → 2.11.2-1
• ros-noetic-joystick-interrupt: 0.17.5-1 → 0.17.6-1
• ros-noetic-map-organizer: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation-common: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation-launch: 0.17.5-1 → 0.17.6-1
• ros-noetic-obj-to-pointcloud: 0.17.5-1 → 0.17.6-1
• ros-noetic-planner-cspace: 0.17.5-1 → 0.17.6-1
• ros-noetic-safety-limiter: 0.17.5-1 → 0.17.6-1
• ros-noetic-track-odometry: 0.17.5-1 → 0.17.6-1
• ros-noetic-trajectory-tracker: 0.17.5-1 → 0.17.6-1
• ros-noetic-ur-client-library: 1.7.1-1 → 1.8.0-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:

• Adam Serafin
• Atsushi Watanabe
• Felix Exner

1 post - 1 participant

Read full topic

Hello guys,
It has been now 2 weeks that I use the new gazebo version (gz) and wow is the doc unhelpfull. Every time I search some thing I find the old version tutorial…
I have a few examples for example :

• I want to know how to use the mesh tag in my .world file and the only tutorial that I found is Pavillon CustomWorld from ArticulatedRobotics.
• How do I use the size tag ? Is it applicable for every geometry ?
• I want to import uri no good explanation how to do it (yes there is a tutorial but it’s not intuitive…
  And a lot more…

I am not here to just say this is bad but I want to know if other people feel lost like me and how can we change this situation ?

Hope I don’t make to many people angry !

5 posts - 5 participants

Read full topic

OSRF Google Summer of Code 2025

Hi Everyone,

I am excited to announce that all of our Google Summer of Code (GSoC) projects for 2025 are now available online in our GSoC Wiki. If you are unfamiliar with GSoC, it is a summer internship program sponsored by Google that is open to undergraduate and graduate students in most countries (see video below). The GSoC program allows students to work with veteran open source developers over the summer to contribute to open source projects.

This year, all five Open Robotics projects (ROS, Gazebo, Open-RMF, ROS Infrastructure, and ROS Control) will participate in GSoC. This will be our only internship opportunity this year, so we made sure to recruit as many mentors as possible. We will also be posting an open internship thread on ROS Discourse in the next couple days.

2025 Open Robotics Projects

This year we will offer sixteen GSoC projects across our five open source projects. These projects will be mentored or co-mentored by sixteen seasoned contributors from the Open Robotics community. I’ve summarized the projects below, but you can read all about them on our project wiki page.

• Gazebo:
  • Gazebo GPU Lidar with @arjo129
  • Gazebo Gaussian Splats with @arjo129
  • Physics-based sonar simulation with @woensug-choi, @rakeshv24, and @mabelzhang
• Open-RMF:
  • Improving UI / UX of Site Editor with @grey and Xiyu Oh
  • Workflow Diagram Editor with @grey and @Luca
  • Multi-Agent Traffic Optimization with @grey and @Luca
  • New Open-RMF Demo Demo with @Aaron_Chong
• ROS:
  • Improved ROS 2 Doctor with @tomoyafujita
  • Structured Parameter Support with @JM_ROS
  • C/C++ Struct to ROS Message Converter with @JM_ROS
  • Improvements to ROS 2 Tracing @christophebedard
• ROS Infrastructure:
  • VCSTool Improvements with @claraberendsen and @jrivero
  • Mixin composition in colcon-mixin with @cottsay and Sean McGrath
  • SDFormat on PyPi with @jrivero
• ROS Control:
  • Mission Control for ROS 2 Control with @bmagyar and @saikishor
  • Hardware Diagnostic Support with @bmagyar and @saikishor

Project Proposals

Student applications for GSoC will be open from 2025-03-24T07:00:00Z UTC→2025-04-08T07:00:00Z UTC. Students must apply using the application form on the official GSoC website.

After speaking with our mentors I want to call out a few things that we’re looking for in student applications. Students applying to our GSoC projects should make sure to highlight the following things in their application:

• We want to see your work, even if it’s not perfect! Please include projects from school, work, or personal initiatives. Include links to your GitHub/GitLab profile and/or a personal project page. We’re looking for students who actively code and improve their skills.
• We prefer students with some open source experience. If you’ve contributed to a FOSS project, or an Open Robotics project, please call that out. We want to see that you are familiar with the process of submitting a pull request to an open source project and working with the maintainer to get that pull request merged. These don’t have to be big pull requests, a single line or character change is fine!
• If you have experience with one of our projects, like ROS or Gazebo, please mention that! Classroom experience is more than sufficient. If you have been to a ROS event (either in person, or virtual) call that out! We’re looking for students who are active ROS users and part of the broader ROS community.
• Our mentors are looking for students with strong written communication skills. Our GSoC students will spend the summer mostly communicating with their mentors via written communications. It is important that students are able to express themselves clearly and succinctly. We ask that students not use large language models to write their project proposals, however using an LLM to check grammar and spelling is acceptable. Our mentors may choose to reject students they suspect used LLMs to write their applications.

Finally, the best way to enhance your GSoC proposal is to connect with our mentors and the ROS community. Consider submitting a pull request to one of our projects. Most Open Robotics project repositories have “Good First Issue” and “Help Wanted” tags in their issue trackers. If you have time, please consider making a small project contribution. For guidance, feel free to join our Discord server.

2 posts - 1 participant

Read full topic

docs.ros.org Got a Facelift!

Hi everyone,

If you’re anything like me, you probably visit docs.ros.org at least five times a day, and you probably also have at least two dozen bookmarks related to ROS development in your browser. It seems like a good portion of onboarding new ROS users is just pointing them to the ROS documentation and our useful resources.

I’ve been trying to fix this problem for quite a while, and I finally have some good news! Thanks to some wonderful open-source design contributions from Shak and Vlad at HelloRobo.co, we’ve put together a new landing page for the ROS documentation. This new landing page should be your one-stop shop for most of your ROS documentation resources, and it renders well on mobile devices!

Don’t worry, the page still points you to the same ROS documentation, but we’ve managed to include just about everything you could need on one handy page! On the new docs.ros.org page, you’ll find:

• The documentation for every ROS release
• Pointers to our ROS calendars and how to add your events
• Links to all of our community resources (Discord, Discourse, Robotics Stack Exchange)
• Links to the ROS distro art and trademark information
• All of our ROS and ROSCon videos on Vimeo
• Links to ROS REPs and ROS package information
• An at-a-glance installation guide for new users
• A whole lot more!

If there’s something you think we missed that belongs there, please don’t hesitate to reach out or send us a pull request.

And thanks again Vlad and Shak for contributing their design skills to the project! And thanks @Nuclearsandwich with the deployment help.

11 posts - 8 participants

Read full topic

Hi everyone,

I’m exploring the idea of using GPS sensor exclusively to guide a mobile robot along predefined line patterns on sports fields (such as soccer fields, tracks, or basketball courts). The goal is to rely solely on GPS data for navigation—without the use of cameras, vision systems, or any additional sensors. Is it possible?

My main objective here is to investigate the weaknesses and limitations of using only GPS for precise navigation. This exploration could serve as a foundation for later expansion by incorporating multiple sensors or technologies, but for now, I want to focus on how far GPS alone can take us.

9 posts - 7 participants

Read full topic