Revision history [back]

It appears bloom tries to push to https://github.com/ros2-gbp/slider_pu... in addition to my own https://github.com/oKermorgant/slider....

The migration tools used to produce new distributions from Rolling will automatically create a new release repository in ros2-gbp if the current release repository isn't already there. Here's the relevant part of the code. This is done to facilitate future distribution-wide automated bloom operations for creating new distributions, such as Humble, or updating the release platforms for Rolling as we did when transitioning the entire distribution to Ubuntu Jammy ahead of the Humble release.

Is there any one I should contact to be able to release a new package on https://github.com/ros2-gbp/*-release ?

As mentioned by @gvdhoorn, in order to manage the maintainer permissions for an organization that everyone now needs access to, we've scripted the permissions setup. The repository for those scripts is ros2-gbp-github-org.

Additionally, are the personal release repositories now obsolete?

For ROS 2 distributions it is strongly recommended that projects, especially those in ROS 2 Foxy and beyond, use the release repositories in ros2-gbp for all releases as this will avoid fragmenting release metadata across multiple repositories since each run of the migration tools will push the new release artifacts exclusively to the ros2-gbp organization repository. For earlier ROS 2 and ROS distributions, using a ros2-gbp repository is a matter of personal preference and convenience. If maintainers would prefer just to maintain all their release repositories there for consistency, I'm fine facilitating that within reason to reduce friction for them. If they prefer to maintain separate release repositories for distributions where it isn't strictly required to use ros2-gbp, I'm equally happy to facilitate that as long as it gets the contemporary and future ROS 2 distributions into the ros2-gbp release organization.

It appears bloom tries to push to https://github.com/ros2-gbp/slider_pu... in addition to my own https://github.com/oKermorgant/slider....

The migration tools used to produce new distributions from Rolling will automatically create a new release repository in ros2-gbp if the current release repository isn't already there. Here's the relevant part of the code. This is done to facilitate future distribution-wide automated bloom operations for creating new distributions, such as Humble, or updating the release platforms for Rolling as we did when transitioning the entire distribution to Ubuntu Jammy ahead of the Humble release.

Is there any one I should contact to be able to release a new package on https://github.com/ros2-gbp/*-release ?

As mentioned by @gvdhoorn, in order to manage the maintainer permissions for an organization that everyone now needs access to, we've scripted the permissions setup. The repository for those scripts is ros2-gbp-github-org.. The issue templates in that repository will hopefully help you form the requests for changes that you need.

Additionally, are the personal release repositories now obsolete?

For ROS 2 distributions it is strongly recommended that projects, especially those in ROS 2 Foxy and beyond, use the release repositories in ros2-gbp for all releases as this will avoid fragmenting release metadata across multiple repositories since each run of the migration tools will push the new release artifacts exclusively to the ros2-gbp organization repository. For earlier ROS 2 and ROS distributions, using a ros2-gbp repository is a matter of personal preference and convenience. If maintainers would prefer just to maintain all their release repositories there for consistency, I'm fine facilitating that within reason to reduce friction for them. If they prefer to maintain separate release repositories for distributions where it isn't strictly required to use ros2-gbp, I'm equally happy to facilitate that as long as it gets the contemporary and future ROS 2 distributions into the ros2-gbp release organization.