-
Notifications
You must be signed in to change notification settings - Fork 190
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
Update BatteryState.msg with temperatures #140
Update BatteryState.msg with temperatures #140
Conversation
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, provided that we create a new "noetic-devel" branch and target that. We also want this in ROS 2; I'll make a separate PR for that.
Essentially a cherry-pick of ros/common_msgs#140 onto ROS 2. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Essentially a cherry-pick of ros/common_msgs#140 onto ROS 2. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
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. ros/rosdistro#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 #139