You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dirk-thomas@mjcarroll it was reported in #406, and fixed in #409 and #410, the bug with string literals and multiline comments in IDL files. The bug was reported on ROS2 Dashing, which is an LTS version that I supposed it should be used to stabilise package APIs using Dashing (which is something I am looking to do).
I see that rosidl package released under 0.8.0 tag are only available under ROS2 Eloquent, and only version 0.7.6 is available to Dashing, which doesn't fix the bug on regarding the multiline comments (string literals).
Is it possible to make the 0.8.0 also available under Dashing, or at least back port the above fixes, in order to address the same bug? Doesn't seem reasonable to bump into a new ROS version in order to solve a bug.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Signed-off-by: Michael Carroll <michael@openrobotics.org>
TSC21
changed the title
rosidl 0.8.0 release to Dashing
rosidl 0.8.0 release to Dashing (or backport string literals fix)
Oct 14, 2019
dirk-thomas
changed the title
rosidl 0.8.0 release to Dashing (or backport string literals fix)
request backporting string literals fix to Dashing
Oct 15, 2019
@dirk-thomas @mjcarroll it was reported in #406, and fixed in #409 and #410, the bug with string literals and multiline comments in IDL files. The bug was reported on ROS2 Dashing, which is an LTS version that I supposed it should be used to stabilise package APIs using Dashing (which is something I am looking to do).
I see that rosidl package released under 0.8.0 tag are only available under ROS2 Eloquent, and only version 0.7.6 is available to Dashing, which doesn't fix the bug on regarding the multiline comments (string literals).
Is it possible to make the 0.8.0 also available under Dashing, or at least back port the above fixes, in order to address the same bug? Doesn't seem reasonable to bump into a new ROS version in order to solve a bug.
Thanks in advance!
The text was updated successfully, but these errors were encountered: