Skip to content
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

Fix jazzy #421

Merged
merged 3 commits into from
Nov 8, 2024
Merged

Fix jazzy #421

merged 3 commits into from
Nov 8, 2024

Conversation

Rayman
Copy link

@Rayman Rayman commented Apr 2, 2024

This PR fixes the change in API for calculateMinAndMaxDistances due to the following PR: ros-navigation/navigation2#3875

This PR buils on top of the changes from: #414

Tony Najjar and others added 3 commits August 16, 2023 17:26
This PR fixes the change in API for `calculateMinAndMaxDistances` due to
the following PR: ros-navigation/navigation2#3875
@Rayman
Copy link
Author

Rayman commented May 8, 2024

Can somebody look at this PR?

@Timple
Copy link

Timple commented Sep 30, 2024

ping?

@Timple
Copy link

Timple commented Oct 11, 2024

pinging @corot as it seems you are the last one who merged something in this repository 🙂

@corot
Copy link
Collaborator

corot commented Oct 12, 2024

pinging @corot as it seems you are the last one who merged something in this repository 🙂

I guess I'm the closest to a maintainer for this repo.... but I'm still stuck with ROS 1, so cannot test this.
I can merge with a leap of faith, but this will break backward compatibility with previous ROS 2 versions, right?

@Rayman
Copy link
Author

Rayman commented Oct 14, 2024

I can merge with a leap of faith, but this will break backward compatibility with previous ROS 2 versions, right?

You should create the following branches:
humble-devel: contains the current ros2-master code
iron-devel: contains this PR: #414
ros2-master should contain #414 + this PR

@renan028
Copy link
Collaborator

I can merge with a leap of faith, but this will break backward compatibility with previous ROS 2 versions, right?

You should create the following branches: humble-devel: contains the current ros2-master code iron-devel: contains this PR: #414 ros2-master should contain #414 + this PR

I have created the humble branch and I will try the PR this week, and sync with @corot
Thank you for the PR

@corot
Copy link
Collaborator

corot commented Oct 18, 2024

I have created the humble branch and I will try the PR this week, and sync with @corot Thank you for the PR

thanks! what about the build farm to create the debians? I guess we need to change to use one branch or the other

also, I would not call it -devel... I expect pretty little additional development here

@renan028
Copy link
Collaborator

renan028 commented Oct 18, 2024

@Rayman
It looks like ros-jazzy-libg2o is not compatible with teb in this version.
g2o::sign was removed (I have checked that it exists on latest release but not in g2o master branch)
Did you manually change to use release to build it?

I have managed to build with this PR: #425

@corot
We will have to update the build farm.
regarding the -devel, I have followed the repo convention.

@corot
Copy link
Collaborator

corot commented Nov 8, 2024

Ok, I finally installed jazzy, so I can take over this
Iron is EOL this month, so I will skip

  • I'll rename master as Humble
  • Merge this and @renan028's PR on master (== jazzy)
    hopefully rolling and jazzy are compatible by now

@corot corot merged commit 94abd58 into rst-tu-dortmund:ros2-master Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants