ROS PMC July 2026: Rolling Sync Policy Approved, Buildfarm Regressions Cleared
Key decisions on sync automation, Cyclone dependency, and human-first issue triage.
The ROS PMC meeting on July 28, 2026, finalized a Rolling sync policy after a week of no negative feedback. The policy, held by @yadunund, enables automatic syncs to main with threshold tightening near releases. @clalancette emphasized monitoring the main branch to avoid syncing garbage. This change frees up time for manual Bloom releases on Rolling, which are still required but now less urgent.
On the buildfarm side, Cyclone jobs were unblocked by adjusting ignore rules for Fast DDS dependencies—the buffer test is safely skipped until Cyclone supports rosidl buffers. The Waffle note-taker board impressed members by filtering contributors to likely humans, reducing AI noise. Rosdistro assignments for July 28-Aug 4 go to @skye.galaxy and @wjwwood. Key packages: OSQP is being forked by MoveIt after TIER IV abandonment; rqt_teleop faces a naming debate with rqt_teleop_twist suggested for specificity.
- Rolling sync policy approved, enabling automatic syncs to main, monitored by @yadunund with tightening near releases.
- Cyclone build regressions resolved by skipping unimplemented buffer test until rosidl support lands.
- Waffle board now filters contributors by human likelihood, speeding up issue triage and reducing AI-generated noise.
Why It Matters
Streamlines ROS Rolling development, reduces manual overhead, and ensures higher quality releases for roboticists.