# 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:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcogg](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/marcogg/32/6613_2.png) [@marcogg](https://discourse.openrobotics.org/u/marcogg)\
**Post date:** [September 7, 2026, 8:43am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926/1 "2026-09-07T08:43:10Z")

</div>

We’re planning a Jazzy Jalisco sync next Wednesday 2026-09-08T16:00:00Z. There are currently [882 packages](http://repo.ros2.org/status_page/ros_jazzy_default.html?q=SYNC)ready to sync and [one regression](http://repo.ros2.org/status_page/ros_jazzy_default.html?q=REGRESSION) that we hope to fix.

If you find any other regression when testing, please report it upstream and leave a comment here so we can track it leading up to the sync.

Starting today 2026-09-06T16:00:00Z we’ll hold all rosdistro PRs unless they fix reported regressions.

---

<div class="post-metadata">

**Author:** ![marcogg](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/marcogg/32/6613_2.png) [@marcogg](https://discourse.openrobotics.org/u/marcogg)\
**Post date:** [September 11, 2026, 3:24am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926/2 "2026-09-11T03:24:48Z")

</div>

The [sync is out](https://discourse.openrobotics.org/t/new-packages-for-jazzy-jalisco-2026-09-11/58027)!

---

<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)

---

<div class="post-metadata">

**Author:** ![peci1](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/peci1/32/10145_2.png) [@peci1](https://discourse.openrobotics.org/u/peci1)\
**Post date:** [September 15, 2026, 11:54am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926/4 "2026-09-15T11:54:57Z")

</div>

Yes, this zenoh bug is very real. It basically makes it impossible to use bag record (stops recording after random amount of time and says no error or warning). I’d say any release with the affected version is broken.

---

<div class="post-metadata">

**Author:** ![marcogg](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/marcogg/32/6613_2.png) [@marcogg](https://discourse.openrobotics.org/u/marcogg)\
**Post date:** [October 2, 2026, 2:55am UTC](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-09-09/57926/5 "2026-10-02T02:55:09Z")

</div>

We’ll make [one happen next monday](https://discourse.openrobotics.org/t/preparing-for-jazzy-sync-2026-10-05/58533).