The ROS PMC meeting for this week was on Tuesday. The notes from the meeting are available at ROS 2 PMC weekly meeting agenda - May 6, 2025
PMC Business
- Formal Decision: Add Jammy as a tier 3 platform for ROS 2 Jazzy
- Add Ubuntu Jammy as a Tier-3 platform. by clalancette · Pull Request #413 · ros-infrastructure/rep · GitHub
- Motion: @christophebedard
- Second: @cottsay
- Passed by consensus
- Formal Decision: Add @emersonknapp as PMC full member now that the mentorship period (starting March 18, 2025) has ended (Article 6.1.iv)
- Motion: @christophebedard
- Second: @wjwwood
- Passed by consensus
Ongoing Tasks
- Buildfarm:
- PTAL: Buildfarm Issues Triage Sheet
- Specifically we still have no resolution on the CycloneDDS issue.
- @ahcorde: We are having a lot of turnover in ci_linux workers leading to a pretty deep queue. Is this normal or can we change the number of workers? This specifically impacts those on European time.
- @claraberendsen : Please let buildfarmers know when you see issues like this. Adding RHEL to the matrix adds more jobs without scaling the workers, which keeps queues more full
- @nuclearsandwich: Traditionally organizations would pay for more CI to accelerate developers, but we are under different constraints. It’s hard to measure if we are over/under provisioning CI.
- In the short term, we can scale up for bigger known workloads (Kilted release)
- Gazebo team is testing auto-scaling
- @mjcarroll: Have we gotten any feedback on the fixed Jetson/RPi arm64 builds.
- Nothing yet, will follow up with community
- PTAL: Buildfarm Issues Triage Sheet
- Waffle assignments:
- May 8 + May 15: @alsora
- Rosdistro Assignments
- May 6 - May 13: @emersonknapp and @christophebedard
- Outgoing rosdistro issues
- @mjcarroll: If an issue is marked “changes requested” or “more information needed”, who is responsible for following up?
- Consensus: Current rosdistro assignees should be checking old issues to see if they have been updated. Naming issues can be brought to PMC meetings.
- @mjcarroll: If an issue is marked “changes requested” or “more information needed”, who is responsible for following up?
- ROS Bosses:
- Audrow (Humble)
- No updates
- Shane (Noetic)
- Sync this week, freeze starts today
- 3rd to last
noeticsync!
- Marco (Jazzy)
- Patch release went out last Wednesday
- Yadu (Rolling)
- No updates
- Audrow (Humble)
Kilted Development
- Testing and Tutorial Party (GitHub - ros2/kilted_tutorial_party)
- 350/563 issues closed (~62%)
- Notable issues:
- RViz crash
- Needs new binary archives
- Connext absent from debs
- RViz crash
- Connext is still absent from arm64 archive
- Connext now supports arm64, but since the packges on the buildfarm don’t support security, we won’t run full CI with it.
- Leave support in place for best-effort community support.
- GurumDDS package import still pending
Agenda Items
- @mjcarroll: Nav2 is missing from kilted (and rolling)
- @sloretz missing from rolling is intentional: RFI: Would you use Nav2 Rolling binaries?
- @smac to do Nav2 release: ros-navigation · Issue #45372 · ros/rosdistro · GitHub
- @DLu New common interface message proposals surfaced from simulation_interfaces work:
- Result.msg: Result.msg for Service Responses by DLu · Pull Request #279 · ros2/common_interfaces · GitHub
- @tfoote: This is a recurring pattern we have seen in ROS 2. Because we are transport independent, we can’t depend on the transport having the ability to do return codes/errors, so doing it in message makes sense.
- @JM_ROS: These seem simulation specific
- @DLu: intended to be a jumping off point for feedback and iteration.
- Feel free to comment and get feedback in.
- Bounds.msg: [shape_msgs] New Bounds Msg by DLu · Pull Request #278 · ros2/common_interfaces · GitHub
- Feel free to comment and get feedback in.
- Result.msg: Result.msg for Service Responses by DLu · Pull Request #279 · ros2/common_interfaces · GitHub
- @HemalShahNV Should all nodes be lifecycle nodes as a first class concept in L-turtle.
- All Nodes as Lifecycle Nodes
- Refer to meeting notes for conversation here. Too much nuance to summarize!
- @mjcarroll RFC: Pixi workflow enhancements:
- @mjcarroll RFC: Automating rosdistro status
- Conclusion: This is a good idea, but opinions on implementation vary. Added a feature here: Automate distribution sync freeze management · Issue #45651 · ros/rosdistro · GitHub
As a reminder, ROS PMC meetings are open to the public, though only committers and members may speak without being called on. If you have topics that you would like discussed, feel free to respond here.