Changes to messages are usually breaking changes and so, should only be done in the main/rolling branch, especially after a package has reached 1.0.0. (see https://docs.ros.org/en/kilted/The-ROS2-Project/Contributing/Developer-Guide.html#versioning). To align ourselves with ROS best practices on branching, we should create a branch for each ROS distro and make releases out of them. We can then limit backports to non-breaking changes.
Changes to messages are usually breaking changes and so, should only be done in the
main/rollingbranch, especially after a package has reached 1.0.0. (see https://docs.ros.org/en/kilted/The-ROS2-Project/Contributing/Developer-Guide.html#versioning). To align ourselves with ROS best practices on branching, we should create a branch for each ROS distro and make releases out of them. We can then limit backports to non-breaking changes.