-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: Upgrade Gazebo from Garden to Harmonic #170
Comments
This is currently being blocked by mavlink/mavros#1958. Once merged, we can resolve this issue. |
|
#220 upgrades Rolling to Harmonic. I could break just the upgrade to Harmonic into a separate PR which you could propagate to Humble and Iron (leaving the Rolling / Noble - specific changes in the existing PR) |
I just double-checked this, and I was wrong. Hypothetically, the backport should still work ( |
So here's a merge of the ROS-Gazebo compatibility matrix and the ROS-Gazebo-ros_gz matrix:
Based on the spotty availability of binaries, what's the desirable endpoint for blue? Here's where we are now:
I assume Rolling is converging with Jazzy (i.e. Harmonic will soon be the preferred version)? |
Here is what I'm thinking:
The reason that I am undecided on Rolling is because it may be nice to switch to new versions of Gazebo as they come out, but I am open to discuss that. Here are the docs on the Iron/Humble/Jazzy Harmonic installation. |
Hm. So I'm stuck on how to implement the switching between ros_gz sources from a git-mergify point of view. How about:
This should work for |
Feature Type
Changing existing functionality in the BlueROV2 driver
Problem Description
The current LTS (Jazzy) and Rolling use Gazebo Harmonic instead of Gazebo Garden.
Feature Description
Upgrade the
main
andjazzy
branches to use this version of Gazebo.Alternative Solutions
N/A
Additional Context
No response
The text was updated successfully, but these errors were encountered: