-
Notifications
You must be signed in to change notification settings - Fork 809
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
[ROS 2][grid_map_core] Update ROS 2 branch with the latest changes from master #486
base: rolling
Are you sure you want to change the base?
[ROS 2][grid_map_core] Update ROS 2 branch with the latest changes from master #486
Conversation
@kjalloul-anybotics rebase, please |
Thanks for the contribution, nice to see some support for bringing the ROS 2 branch up to date! As it stands, you've bundled a number of unrelated changes. Can you instead propose PR's that target things individually so it's more reviewable? Also, bumping the version can be done as it's own PR. In addition to the changes outlined, you have
That's a lot of risk, with no linkage to the original commit history or PR's. Perhaps there's a better strategy we can come up with to make this safer? |
Thanks for the feedback! Yes in the beginning I only needed one new function in But you're right it definitely can be broken down into smaller PRs to keep track of where the changes came from. I traced back the origin of most changes to these commits:
Do you think it's a good idea to create separate PRs for each of them? Once And apparently |
Awesome, thanks for putting the list together! yes, if it's easy enough, separate PR's are preferred, with a link to the ROS 1 PR. The change to ifdefs was probably intentional, and no one has complained about it, so I'd personally vote we just not touch it. |
Changes to
grid_map_core