-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove old Gazebo stuff once new gazebo lands #4386
Comments
Can you enumerate these please in a checklist! That way we don't miss anything in a couple of weeks |
Let's put it that way: grep for (easier than listing every instance) |
👍 Just as long as when we move on and forget the details we know what to do. Sounds good hah |
@SteveMacenski is the main still pointing to rolling? I am having many issues trying to simulate building the docker for ros rolling. Does nav2 still support rolling, when we develop for main, should it be based on rolling?.
|
The system tests in rolling are commented out since we do not have a working simulation in new-gazebo yet. We would love the help though if interested :-) There's alot of moving parts and there's some activities that are parallelizable |
Sure, It is a blocking m development also so jajajaja. I would need more context though |
This gets the ball rolling #3634 with a TB3 sim but isn't released in binaries for us to be able to use in Nav2 so I think my current thought process is to:
So the TB3 stuff in the fork + doing the system tests could be parallelized with me getting the TB4 stuff completed and ready for bringup, if you were open to helping! |
For now understood, will probably ask for more info later, but this should be good for a starting point |
Beyond the simple commander and system tests that need to be ported (see #4399) this is done. Closing |
In #4298 we commented out stuff from old gazebo to get CI up and running. This task is a reminder to clean those up new gazebo is up and running.
The text was updated successfully, but these errors were encountered: