ROS PMC Minutes for February 24, 2026

The ROS PMC meeting for this week was on Tuesday. The notes from the meeting are available at ROS PMC weekly meeting agenda

ROS PMC Business

Regular Business

Buildfarm update

The buildfarm is responsible for building and testing the thousands of packages in the ROS ecosystem across different distributions and platforms. This section tracks regressions, infrastructure issues, and high-priority triage items.

Waffle note-taker

Waffle is a weekly meeting where maintainers triage incoming issues and pull requests that haven’t been otherwise acted upon. One person per week is assigned to be the “waffle note-taker” to both take notes in the meeting to keep the meeting as efficient as possible.

Rosdistro assignments

Rosdistro is a weekly assignment to monitor incoming issues and pull requests in GitHub - ros/rosdistro: This repo maintains a lists of repositories for each ROS distribution. Two people per week are assigned to be the rosdistro maintainers.

Release Management

Each active ROS distribution has a designated “release manager” (or “ROS Boss”) who oversees the sync and patch release cycle to ensure stable updates are delivered to users regularly.

  • @christophebedard (Humble)
  • @yadunund (Rolling)
    • Rolling in sync hold due to 100+ regressions from ament_target_dependencies removal.
    • [@sloretz] raised a discussion on the necessity of Rolling syncs vs. ros2-testing only.
  • @marcogg (Jazzy)
    • No updates.
  • @cottsay (Kilted)
    • Planning a sync this week or early next week.

Working Groups

  • Client Library Working Group (@alsora)
    • Meeting last Friday.
  • Accelerated Memory Transport Working Group (@ahcorde)
    • Meeting last Wednesday (2026-02-25).
  • ROSGraph Working Group (@emersonknapp)
    • Meeting next Tuesday (2026-03-03).
  • Lyrical Release Working Group (@sloretz)
    • Meeting this Friday (2026-02-27).

Agenda

  • Wiki.ros.org Long-term Plan [@claraberendsen]
    • Plan to transition to a static site 6-12 months after ROS 1 EOL. Coordination with Tully/Kat underway.
  • URDFDOM Maintenance [@cottsay]
    • Discussion on moving urdfdom and urdfdom_headers maintenance to the ROS Controls PMC.
  • Community Engagement & Office Hours [@mjcarroll / @Katherine_Scott]
    • Proposing a soft launch for “ROS Office Hours” on Friday mornings to facilitate PR reviews and community collaboration.
  • GSoC 2026 [@Katherine_Scott]
    • Accepted! Mentors and project proposals are needed. Wiki is open for submissions.
  • Lyrical Technical Transitions [@sloretz]
    • C standard moving to C17.
    • [@sloretz] REP 2000 migration to ROS 2 docs.
    • [@claraberendsen] Resolute platform updates: addressing regressions in rosbag2, launch_pytest, and flake8 import orders.
  • CI Improvements [@MiguelCompany]
    • Adding a CI_USE_ZENOH checkbox to the launcher.
    • Improving RMW implementation testing guards for Cyclone DDS PRs.

Action Items

  • @everyone
    • Spend an hour this week triaging repositories and marking 2-4 hour tasks as “good first issue” for GSoC.
    • Think about and submit GSoC project ideas to the wiki.
  • @ahcorde
    • Provide a list of packages with no progress vs. patches vs. fixed for the Rolling sync.
    • Continue working on patches for Rolling sync regressions.
    • Follow up on QT6 transition reviews.
  • @clalancette or @MichaelOrlov
    • Release MCAP so rosbag2 PR can point to the updated version.
  • @claraberendsen
    • Coordinate with @Katherine_Scott on moving wiki.ros.org to a static site.
    • Open issue for launch_pytest build regression with PyTest 8.
    • Open issues for import order regressions across affected packages.
  • @Katherine_Scott
    • Review @sloretz’s REP 2000 PR by end of the week.
  • @mjcarroll
    • Create Zoom meetings and calendar invites for Lyrical WG and Friday office hours.
    • Post nanoBind dev package version mismatch issue on PMC chat.
    • Stay on ROS distro duty for an extra week.
    • Follow up with @MiguelCompany regarding AMT WG recordings.
    • Flag the Cyclone DDS PR for proper RMW testing.
  • @sloretz or @claraberendsen
    • Add checkbox for Zenoh in CI launcher.
  • @skye.galaxy
  • @yadunund
    • Proceed with Rolling sync and identify packages with regressions.