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.

Sign up for GitHub

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

Jump to bottom

[ROS2] Consider branching out to dashing-devel #10

Closed
Karsten1987 opened this issue May 28, 2019 · 1 comment
Closed

[ROS2] Consider branching out to dashing-devel #10

Karsten1987 opened this issue May 28, 2019 · 1 comment

Comments

@Karsten1987
Copy link

Given the latest changes in ROS2 for the dashing release, I believe it makes sense to branch out to a dashing-devel branch.

One of the changing is for example the exposure of history-depth as a QoS.
@Karsten1987 Karsten1987 mentioned this issue May 28, 2019
Closed
@dirk-thomas
Copy link
Contributor

Until there is a change proposed in a PR which is necessary for Dashing but not compatible with Crystal there is no need for branching.

@Karsten1987 Karsten1987 mentioned this issue May 28, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dirk-thomas @Karsten1987