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

Move mbf_msgs into it's own git repo #190

Open
jspricke opened this issue Apr 27, 2020 · 4 comments
Open

Move mbf_msgs into it's own git repo #190

jspricke opened this issue Apr 27, 2020 · 4 comments

Comments

@jspricke
Copy link

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.

@spuetz
Copy link
Member

spuetz commented Apr 27, 2020

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.

@jspricke
Copy link
Author

hm.. breaks our internal tooling ;)

@Rayman
Copy link
Contributor

Rayman commented May 1, 2020

For the maintainers it saves a lot of time keeping everything in one repo

@jspricke
Copy link
Author

jspricke commented May 1, 2020

@Rayman that's not really true, also look at other ROS packages, like common_msgs, control_msgs or moveit_msgs.

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

No branches or pull requests

3 participants