Hi Daniel,
Thank you for reaching out and your interest. You can find here the answers to your questions:
-
- The release of new tracks will be aligned with the major releases of ROS 2. This means that there will be a new Vulcanexus track for each Vulcanexus snap when a new version of ROS 2 is released, which takes place once a year around April-May (as it’s happening now with ROS 2 Iron).
-
- We follow the same lifecycle than ROS 2, so when a ROS 2 distribution is end of life ours will be as well. We will follow this calendar (ROS 2 calendar): https://docs.ros.org/en/rolling/Releases.html. This means that we’re committed to support Vulcanexus Humble until May 2027 and Vulcanexus Iron until November 2024.
-
- Backwards compatibility between tracks cannot be guaranteed, as ROS 2 doesn’t guarantee it. So even if the user data does not change and DDS is compatible, things like discovery, native headers, etc. that do break compatibility can change in ROS 2. That way, Vulcanexus will have the same backwards compatibility as ROS 2.
Hope these answers are helpful, but if you have any other questions or need more info do not hesitate to let us know, we’ll be happy to help
Thanks!