ouster-ros: 0.10.3-1 in 'iron/distribution.yaml' [bloom]

[Samahu]

Increasing version of package(s) in repository ouster-ros to 0.10.3-1:

• upstream repository: https://github.com/ouster-lidar/ouster-ros.git
• release repository: https://github.com/ouster-lidar/ouster-ros-release.git
• distro file: iron/distribution.yaml
• bloom version: 0.11.2
• previous version for package: null

ouster_msgs

* Add per package LICENSE file
* Contributors: Ussama Naal

ouster_ros

* Add per package LICENSE file
* manifest symbolic links as files
* Contributors: Ussama Naal

[Yadunund]

The linked release repo does not appear to be public.

And could you clarify the intention behind this PR #38252 which seems to release the same pkgs but under a different repo name?

[Samahu]

Hi @Yadunund I just made the repo public. But during my review of the documentation it says that it is recommended that you create or host the release repository under https://github.com/ros2-gbp. How would I achieve that? Can we move the current release repository on https://github.com/ouster-lidar/ouster-ros-release to live under https://github.com/ros2-gbp later on?

Note that I have opened an issue to create a release team for Ouster: ros2-gbp/ros2-gbp-github-org#308

[Samahu]

I have closed the PR #38252. This was my initial attempt to manually add the repo before I figured out that the bloom toolset would actually generate the pull request for you.

[ros-discourse]

This pull request has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/ouster-driver-package-removed-from-iron/32943/2

[tfoote]

Please open a new issue on the organization management repository: https://github.com/ros2-gbp/ros2-gbp-github-org

There's a template for New Repository to create the ros2 release repo. It's highly recommended for Iron and mandatory for Rolling.

[Samahu]

Please open a new issue on the organization management repository: https://github.com/ros2-gbp/ros2-gbp-github-org

There's a template for New Repository to create the ros2 release repo. It's highly recommended for Iron and mandatory for Rolling.

will do.

[Samahu]

Please open a new issue on the organization management repository: https://github.com/ros2-gbp/ros2-gbp-github-org

ros2-gbp/ros2-gbp-github-org#315

[Samahu]

Should I submit a new PR using bloom since we are changing the location of the release repository for ouster per ros2-gbp/ros2-gbp-github-org#315 from github.com/ouster-lidar org to github.com/ros2-gbp/ org?

[ros-discourse]

This pull request has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/ouster-driver-package-removed-from-iron/32943/6

[tfoote]

I believe that the release repository should be able to be imported and then this PR just edited to point to the new repository location.

[Samahu]

sounds good

…

On Thu, Aug 17, 2023 at 1:32 PM Tully Foote ***@***.***> wrote: I believe that the release repository should be able to be imported and then this PR just edited to point to the new repository location. — Reply to this email directly, view it on GitHub <#38253 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAET6UIKVK5T4CD2PMSAZG3XVZ5W3ANCNFSM6AAAAAA3R2SYVI> . You are receiving this because you authored the thread.Message ID: ***@***.***>