-
Notifications
You must be signed in to change notification settings - Fork 123
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
Fuse -> ROS 2 Rolling Porting Progress #276
Comments
This was referenced Oct 7, 2022
3 tasks
This was referenced Oct 8, 2022
This was referenced Nov 7, 2022
This was referenced Nov 15, 2022
This was referenced Dec 1, 2022
Merged
This was referenced Dec 30, 2022
This was referenced Jan 22, 2023
Merged
Fuse functionality is now ported! 🎉 There's still some linting and docs porting to do EDIT: Those are DONE!! |
This was referenced Jan 28, 2023
Merged
This was referenced Jan 28, 2023
@methylDragon Is there anything left to do before closing this ticket? |
I think we're done here! Ticket closed!! |
This was referenced Feb 7, 2023
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This issue tracks the progress of the ROS 2 port for Fuse, targeting the
rolling
release of ROS 2.Some of the work here will be based off the work mentioned in #257.
Architectural Decisions
I will be prioritising API consistency between the ROS 1 and ROS 2 versions of Fuse. This means I won't be looking at high level architectural changes at this time.
Approach
PRs will be sent against the
rolling
branch on fuse and tf2_2d, working up the dependency graph and doubling back as necessary. (Or more likely, finding features to port as I work up the dependency graph, and port them for downstream packages as well.)Changes in dependent packages that have to be made as a result of a change in a dependency packages will be made on a best effort basis, but can't be confirmed until they're buildable, so expect bugs in those PRs.
I fully expect
fuse_core
to take up the bulk of the migration effort. And I also fully expect needing to circle back after things finally build and run.Progress
General
Port messages fuse -> ROS 2 fuse_core : Messages and Services #285(DEFERRED to on a per-package basis)BONUS (if time permits)
Down (Up?) The Dependency Tree
Additional Notes
The text was updated successfully, but these errors were encountered: