Closed reinzor closed 4 years ago
ping
This looks like a reasonable addition. Changing a core message like this is not something that we can do during a release cycle so we will need to target Noetic. And it would be good to make sure to clearly document any migration requirements for existing users, both for requirements for their code base as well as bag migration rules for logged data.
Can this be closed or do you still require this?
I think this is a good idea to do; thanks for pinging. Now that we are heading towards noetic, I'd create a new branch (noetic-devel), retarget this there, and then merge it. @tfoote any thoughts? If not, I'll just go ahead and do it.
All right, I've created a new noetic-devel branch, then retargeted this PR at that branch. I'm going to go ahead and merge it now. We'll also need an update to https://github.com/ros/rosdistro/blob/master/noetic/distribution.yaml to update the branches there, which I'll do shortly.
Thanks!
Branch change upstream for cross reference. https://github.com/ros/rosdistro/pull/24094
This has not been released into Noetic. Doing so after the release breaks the interface.
Just to keep things connected: this PR has come up on ROS Answers: How to receive standard message that has changed format in noetic?.
Resolves https://github.com/ros/common_msgs/issues/139