You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once Rolling rolls over for ROS 2 Jazzy, we'll default to using sdformat14.
How should we handle branches in sdformat_urdf? Currently, there's a galactic and a ros2 branch, where the former supports Galactic and everything below. So one option is creating an iron branch and updating ros2 to support newer defaults.
@sloretz How are things typically done in the ROS 2 ecosystem or any other more preferable options?
If we don't have the time for all those goals, then I'd recommend the priority being updating Rolling first, then Humble since it's LTS, and lastly Iron as a nice to have.
I think we could get there by doing the following:
Create a branch called rolling pointing to the same commit as ros2
Update the rolling branch until it supports Gazebo Fortress (unless it does already, then no work to do here)
Create a humble branch and an iron branch off of rolling
Update the rolling branch to support Gazebo Harmonic
There will be some cleanup work too of updating source branch entries in ros/rosdistro and making bloom releases.
Once Rolling rolls over for ROS 2 Jazzy, we'll default to using
sdformat14
.How should we handle branches in
sdformat_urdf
? Currently, there's agalactic
and aros2
branch, where the former supports Galactic and everything below. So one option is creating aniron
branch and updatingros2
to support newer defaults.@sloretz How are things typically done in the ROS 2 ecosystem or any other more preferable options?
CC: @azeey
The text was updated successfully, but these errors were encountered: