Update roboception release repositories. #32077
Conversation
These release repositories were forked into ros2-gbp for the Galactic migration in April 2021. Some packages have not been released into the upstream repository since but some have. For the packages which have had releases these have been merged into the ros2-gbp branch on 2022-02-07. Since the [upcoming Rolling platform migration](#32036) will again branch the release repositories into ros2-gbp I recommend that we update them pre-emptively to reduce churn in the bloom configuration branches.
github-actions
bot
added
the
rolling
|
FYI @flixr |
|
Sounds good to me! |
|
@nuclearsandwich what about the packages that are still in the roboception gbp repo (rcdiscover and rc_reason_clients)? |
Yes. The first pass that I've done was specifically to cover repositories which have been moved to ros2-gbp previously but then moved back to their external repositories before we were able to communicate with the maintainers about the changes (that's on us not you). In order to get the Jammy transition done with all reasonable haste I am waiting to update release repositories that aren't in that situation (that is, have not yet been copied into ros2-gbp but will be) once we've done the transition we'll be reaching out to maintainers about the newly copied release repositories with info about the switch and access to the appropriate repositories in ros2-gbp. |
nuclearsandwich
deleted the
nuclearsandwich/roboception-release-repositories
branch
These release repositories were forked into ros2-gbp for the Galactic migration in April 2021.
Some packages have not been released into the upstream repository since but some have.
For the packages which have had releases these have been 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 I recommend that we update them pre-emptively to reduce churn in the bloom configuration branches.