Update transport_drivers release repository. #32082
Conversation
github-actions
bot
added
the
rolling
The release repository was forked into ros2-gbp for the Galactic migration in April 2021. Since then there have been releases into the upstream release repository. These releases were merged into the ros2-gbp branch on 2022-02-07. Since the upcoming Rolling platform migration will again branch the release repositories into ros2-gbp and the ros2-gbp repository is now up-to-date with the external repository I recommend that we update the release repository pre-emptively to reduce churn in the bloom configuration branches.
nuclearsandwich
force-pushed
the
nuclearsandwich/transport_drivers-release
branch
from
fc8fc13 to
ce7f958
Compare
|
@nuclearsandwich In-general, are you OK with me just transitioning to using the |
Yes. I think there's some potential value in keeping ROS 1 and ROS 2 releases separate from a ref count perspective but usage of ros2-gbp for all ROS 2 releases is a bigger priority and if keeping ROS and ROS 2 releases in a single repository is easiest for maintainers I'm all for it. |
The release repository was forked into ros2-gbp for the Galactic migration in April 2021. Since then there have been releases into the upstream release repository.
These releases were merged into the ros2-gbp branch on 2022-02-07.
Since the upcoming Rolling platform migration will again branch the release repositories into ros2-gbp and the ros2-gbp repository is now up-to-date with the external repository I recommend that we update the release repository pre-emptively to reduce churn in the bloom configuration branches.