-
Notifications
You must be signed in to change notification settings - Fork 154
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
Move mbf_msgs into it's own git repo #190
Comments
Hey ;) Are there more reasons for doing that? Because, we have a couple of other issues to solve and I like it to have it all in the same repo. I wouldn't count the versioning as a strong argument. :D Cheers. |
hm.. breaks our internal tooling ;) |
For the maintainers it saves a lot of time keeping everything in one repo |
@Rayman that's not really true, also look at other ROS packages, like common_msgs, control_msgs or moveit_msgs. |
Hi,
currently mbf_msgs are part of the mbf repo, meaning that they get a new release whenever you do a new mbf release. That's not needed and is irritation cause messages are an external interface.
Please move them to a new repo.
The text was updated successfully, but these errors were encountered: