Closed MichaelOrlov closed 3 months ago
We could just merge #106, since it has those changes.
@christophebedard I would prefer to fix CI scripts in a separate PR.
Sure, that's fine with me.
https://github.com/Mergifyio backport jazzy
backport jazzy
@christophebedard @clalancette There is no jazzy
branch for topic_tools
. Did we miss something?
This repo isn't part of the ROS 2 core, and no one created the branch.
When we do create the jazzy
branch, we should update the branch name in rosdistro https://github.com/ros/rosdistro/blob/258800ad9291feb269da3fcbbe8764b98fc94a6b/jazzy/distribution.yaml#L7595 and in the release repo https://github.com/ros2-gbp/topic_tools-release/blob/d3ec3544366ec4e953ca4d5c899e70b4ed5919d9/tracks.yaml#L80
jazzy
branch from rolling
in this repo, and add protection here: https://github.com/ros-tooling/topic_tools/settings/branchesversion: rolling
in the rosdistro jazzy/distribution.yaml
entry for topic_tools
to version: jazzy
: https://github.com/ros/rosdistro/blob/258800ad9291feb269da3fcbbe8764b98fc94a6b/jazzy/distribution.yaml#L7595-L7612devel_branch
for Jazzy from rolling
to jazzy
in the release repo: https://github.com/ros2-gbp/topic_tools-release/blob/d3ec3544366ec4e953ca4d5c899e70b4ed5919d9/tracks.yaml#L95At this point, Rolling and Jazzy will still have the same version of topic_tools
, which is fine.
rolling
, bumping the major versionjazzy
, bumping the minor version