perception_open3d: 0.1.1-1 in 'rolling/distribution.yaml' [bloom]

[SteveMacenski]

Increasing version of package(s) in repository perception_open3d to 0.1.1-1:

• upstream repository: https://github.com/ros-perception/perception_open3d.git
• release repository: https://github.com/ros-gbp/perception_open3d-release.git
• distro file: rolling/distribution.yaml
• bloom version: 0.11.1
• previous version for package: null

[SteveMacenski]

Blacklist for RHEL added due to lack of open3d key ros2/ros_buildfarm_config#244

[wep21]

As for versions, it may be better to make the rolling one greater than the humble one.

[clalancette]

Besides the comment inline, I agree that it does feel a little weird to have Rolling behind Humble. It's not wrong, per-se, but it is confusing. Again, if you want to continue anyway, just let me know.

[clalancette]

FYI, we highly recommend that you use a release repository in https://github.com/ros2-gbp for Rolling. If you don't do this, then this package can't automatically be rolled over into the next distribution.

I won't outright block on this, but let me know explicitly if you want to stay with your current release repository.

[SteveMacenski]

ros-perception/perception_open3d#24 conversation is in the works, I need access to the org to do so. I'm a member of the org but not admin to move / create new repositories which I need to transfer this project (and probably several others in the future)

[SteveMacenski]

Either way, once the repo is transferred, github will automatically redirect to the new location without breaking the ROS (1) link version

[clalancette]

While GitHub redirection will work, I'm not sure whether our tools will follow that properly. @nuclearsandwich can answer that. The easiest thing to do here is to move it over and just use the ros2-gbp repository, that way there is no question. I'll see what I can do about getting ros-perception/perception_open3d#24 resolved.

[SteveMacenski]

OK

[SteveMacenski]

Next Rolling update I'll push past Humble, but right now its actually not head of it in any particular way so just a minor version update for release. Once it surpasses Humble's version, it'll be assigned 0.3.x to be given to iron. Its maybe not super clear to others, but it helps me keep track of Rolling ahead/behind of released versions