-
Notifications
You must be signed in to change notification settings - Fork 9
[Humble] Proposal to add support for managing simulation worlds (backport #4) #15
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
base: humble
Are you sure you want to change the base?
Conversation
@zakmat please keep the authorship of the worlds PR as is |
8759a9d
to
9a67e81
Compare
9a67e81
to
d9f9ce9
Compare
Co-authored-by: Martin Pecka <[email protected]> Co-authored-by: Adam Dąbrowski <[email protected]> Co-authored-by: Mateusz Żak <[email protected]> Signed-off-by: Mateusz Żak <[email protected]>
d9f9ce9
to
63a5e91
Compare
After internal discussion, I have opted to remove modification to Spawnable since modifying the struct layout is not technically ABI compatible. |
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.
Thanks for the backport changes @zakmat!
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.
Thanks for keeping this backward compatible. The changes look good to me.
On the use of Resource
in Spawnable, does it actually make sense for the simulator to return a resource_string
? I would think it would only be used as an input to the simulator.
@@ -2,7 +2,7 @@ | |||
<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> | |||
<package format="3"> | |||
<name>simulation_interfaces</name> | |||
<version>1.0.1</version> | |||
<version>1.1.0</version> |
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.
It's common to use catkin_generate_changelog
and catkin_prepare_release
to bump the versions (https://docs.ros.org/en/kilted/How-To-Guides/Releasing/Subsequent-Releases.html#ensure-repositories-are-up-to-date). Should we do that here and generate changelogs?
This is a back-port of #4 into Humble.
Worlds are new functionality. To avoid breaking changes in existing interfaces we can't use Resource there. To limit the gap with 2.0.0 I am introducing
string resource_string
intoSpawnable.msg