# Preparing for Jazzy Sync 2026-09-09

**URL:** <https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926>\
**Category:** Packaging and Release Management\
**Tags:** ros2, sync, jazzy\
**Created:** [September 7, 2026, 8:43am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926 "2026-09-07T08:43:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![130s](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/130s/32/21_2.png) [@130s](https://discourse.openrobotics.org/u/130s)\
**Post date:** [September 15, 2026, 10:19am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926/3 "2026-09-15T10:19:50Z")

</div>

@marcogg Thanks for the sync.

What’s the plan for the next sync?  
The issue [Lost wakeup: check\_and\_attach\_condition() clears wait\_set\_data-\>triggered without holding condition\_mutex (regression from #1005) · Issue #1032 · ros2/rmw\_zenoh · GitHub](https://github.com/ros2/rmw_zenoh/issues/1032) broke some of Zenoh usecases.  
Looks like `rmw_zenoh_cpp` 0.2.11, which includes the fix, is already released and made into rosdistro [rmw\_zenoh: 0.2.11-1 in 'jazzy/distribution.yaml' [bloom] by Yadunund · Pull Request #53921 · ros/rosdistro · GitHub](https://github.com/ros/rosdistro/pull/53921) but jazzy 9-11 sync included 0.2.10, which seems to break the usecase of the team I’m working with.

* * *

UPDATE: Seems noted in PMC [ROS PMC Minutes for September 15, 2026](https://discourse.openrobotics.org/t/ros-pmc-minutes-for-september-15-2026/58167)

---

_[View the full topic](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926)._
