-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update release repository url for acado_vendor. #32065
Conversation
This release repository was forked into ros2-gbp for the Galactic migration in April 2021 and has not been released into the upstream repository since. Since the upcoming Rolling platform migration will again branch the release repository into ros2-gbp I recommend that we update it pre-emptively to reduce churn in the bloom configuration branches.
@JWhitleyWork FYI |
@nuclearsandwich Could you also add |
@nuclearsandwich Does it make more sense to update the current release repo? |
It makes the most sense for the the ros2-gbp release repositories to be used for all ROS 2 distributions. The Rolling distribution will always need to maintain the ros2-gbp copy of the release repository so that migrations like this one can be run with a target repository that the automation can push to and future ROS 2 distributions created from Rolling will all start out with release repositories in the ros2-gbp organization. |
@nuclearsandwich Thanks for the info! I'll try to go through and make sure all my covered repos have this set correctly (hopefully save you some time). |
I'm grateful for the initiative. In general the current state of Rolling is frozen pending this transition so there will be aftermath no matter what. The repositories I worked on today were in a special case of already having a ros2-gbp release repository from a previous migration (usually the original creation of Galactic) but which weren't using that repository on Rolling. There is a larger pool of repositories that are not currently hosted in ros2-gbp which will get a similar message after the migration. |
Done in #32092 |
@nuclearsandwich Thank you for creating the release repository. |
I'm going to wait to handle this request since I'll be publishing a new mechanism that will allow me to better track them and keep them from being spread around in unrelated issues and pull requests. |
This release repository was forked into ros2-gbp for the Galactic migration in April 2021 and has not been released into the upstream repository since.
Since the upcoming Rolling platform migration will again branch the release repository into ros2-gbp I recommend that we update it pre-emptively to reduce churn in the bloom configuration branches.