-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
cob_manipulation: 0.7.5-1 in 'noetic/distribution.yaml' [bloom] #27682
Conversation
holding for the upcoming Noetic sync |
@nuclearsandwich |
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/preparing-for-noetic-sync-2020-12-14/17835/2 |
Shoot, I missed this before the weekend. I would have been fine with putting it in since it's a brand new package, but I'd rather not delay the sync now to wait for these packages to build on the build farm. |
@sloretz well now that the sync is out...is there anything else that is blocking this PR from being merged? |
Nothing blocking it. I do notice the upstream repository doesn't have any LICENSE files. The review guidelines say to require them of new packages, but maybe it would be fine to merge as is since it's already been released to earlier distros. @nuclearsandwich, @clalancette, thoughts? |
I like using our review guidelines to iteratively improve the situation from release to release. Ideally we would hold it for that. |
none of the care-o-bot repos has any such file and this has not been requested for any of those repos...this pr is the very final pr for the care-o-bot series...this repo has already been released for kinetic, melodic for years... maybe this also, since I'm no longer working for Fraunhofer IPA who hosts these repos, I fear this will take a long while to settle - if at all |
so this PR will not be merged then? @nuclearsandwich @sloretz @clalancette I'd just need a decision because then I would work around this missing release... EDIT: |
I have been interpreting the review guidelines as only blocking for brand new packages (not packages that already exist in a ROS distribution). In this case, I don't think we need to block on having a LICENSE file. Of course, if possible it would be good to get a LICENSE file added. Thoughts? |
Given the circumstances, I'm going ahead with merging this. Hopefully the ticket for adding a LICENSE file will be resolved before the next release. |
Increasing version of package(s) in repository
cob_manipulation
to0.7.5-1
:noetic/distribution.yaml
0.10.0
null
cob_collision_monitor
cob_grasp_generation
cob_lookat_action
cob_moveit_bringup
cob_moveit_interface