Quick poll: Am I the only one who wants matching ROS 2 & Gazebo names?

Hey everyone!

This might seem like a minor detail, but it’s something I’ve noticed while setting up environments.

Why don’t ROS 2 and Gazebo share the same alphabetical codenames? For example, ROS 2 Humble (H) uses Gazebo Fortress (F). It feels a bit counterintuitive, especially for new users.

My thought:

Wouldn’t it be easier if they matched (like Humble Harmonic)? It would simplify remembering which versions go together.

My guess:

I assume the dev team locks the Gazebo version based on what’s stable at release time, rather than picking a name that matches the alphabet. But I’m curious—am I missing a technical reason?

1 Like

Yes. The LTS releases are currently not aligned (Gazebo has odd years, ROS has even years). But there was discussion about aligning them: Public view of Open Source Robotics Foundation | Zulip team chat

3 Likes

Since each Gazebo release is supported by the next ROS distribution released the following May, why not have the Gazebo version released in a given year use a codename whose initial letter matches that of the ROS distribution to be released the following year—thereby creating a clear naming correspondence that reflects their support relationship?

1 Like

See Proposal for a new Gazebo Release Cadence .