rcl_logging_syslog ends up having the each distribution branch such as jazzyiron and humble.
this is only because https://github.com/ros2/rcl_logging/tree/rolling/rcl_logging_interface is not guaranteed to be compatible since during development we modify and change the interfaces time to time.
it is unlikely but that happens, and actually rcl_logging interface is different between iron and jazzy.
rcl_logging_syslog
ends up having the each distribution branch such asjazzy
iron
andhumble
. this is only because https://github.com/ros2/rcl_logging/tree/rolling/rcl_logging_interface is not guaranteed to be compatible since during development we modify and change the interfaces time to time. it is unlikely but that happens, and actually rcl_logging interface is different betweeniron
andjazzy
.the thing is that most of the implementation in
rcl_logging_syslog
can be backported to all distro branches unless that is related to the interfaces. for doing backport, currently we have manual operation with Mergifyio. it would be probably nice to have automatic backport process using either https://github.com/ros2/ros2_documentation/blob/rolling/.mergify.yml or https://github.com/marketplace/actions/backporting