Hi all,
On 2026-04-07T06:59:00Z, we will freeze all RMW-related packages to prepare for the upcoming Lyrical Luth release on 2026-05-22T07:00:00Z.
Once this freeze takes effect, we will not accept new features to the RMW packages until Lyrical branches from ROS Rolling. This restriction applies to the following packages and vendor packages:
We still welcome bug fixes after the freeze date.
Find more information on the Lyrical Luth release timeline here: ROS 2 Lyrical Luth (codename ‘lyrical’; May, 2026).
3 Likes
Friendly reminder that the ROS Lyrical RMW freeze is today, about 15 hours from now.
1 Like
The ROS Lyrical release has now reached RMW Feature freeze. However, there are significant issues with all 4 of ROS Lyrical’s Tier 1 RMW implementations. I will raise these issues in the ROS PMC meeting to decide what to do about them.
The ROS Lyrical RMW freeze is delayed by 1 week: Delaying Lyrical RMW and Feature Freezes
Is the information at Lyrical Luth (codename ‘lyrical’; May, 2026) — ROS 2 Documentation: Rolling documentation up to date? It currently states:
The default middleware in ROS Lyrical is rmw_fastrtps_cpp.
Is this true? I was under the impression that the next LTS release would use rmw_zenoh_cpp and I was looking very much forward to having a better “out of the box” performance with the Zenoh RMW. I cannot find reliable sources claiming that Zenoh will be the default, so maybe this was just wishful thinking and the only goal was to make it “Tier 1”.
Are there such efforts to eventually make rmw_zenoh_cpp the default RMW in ROS 2?