We have branched Humble from Rolling! This means that (1) Rolling is now unfrozen, and that (2) we’ve entered the “beta” testing phase of the Humble Release.
This means that feature and bug fixes can once again be merged into Rolling. Thanks everyone for your patience!
Testing the Humble Beta
If you’d like to help with beta testing Humble, you can find installation instructions here. Currently, we have binary packages for Ubuntu Jammy, with RHEL 8 support on the way. I’ll comment on this post when RHEL 8 binaries are available.
For testing, we suggest that you try to use Humble in parts of your existing ROS 2 codebase. If you’re having trouble or think that you’ve discovered a bug, here are the general steps:
Think about what package is most likely at fault and find its repository.
Check the repository for an issue or PR that describes or fixes the bug you’re seeing.
If there’s no issue or PR, please make an issue with steps to help us reproduce the bug. If you like and you know what to do, feel free to make a PR fixing the issue. You’ll have our thanks at Open Robotics
Releasing your packages
If you maintain a package that you would like to release in ROS 2 Humble Hawksbill, we encourage you to do so by following the guide to releasing a ROS 2 package with bloom. For Humble, the minimum required version of bloom is 0.11.0.
I just set up a machine to do some initial testing for Humble on Ubuntu 22.04 (jammy). When I add the archive at http://packages.ros.org/ros2/ubuntu jammy The name of the ros* packages all still seem to be ros-rolling-* for the current beta.
I see that Humble has Debian Bullseye as a tier 3 supported platform. Is there any chance that the setup via debian package install will be supported on this platform? I’m specifically interested in arm64 packages for ros-humble-base.
Tier 3 platforms are those for which community reports indicate that the release is functional. The development team does not run the unit test suite or perform any other tests on platforms in Tier 3. Installation instructions should be available and up-to-date in order for a platform to be listed in this category. Community members may provide assistance with these platforms.
I’m currently working on a branch ( Work-in-progress, don’t expect it work out of the box) to bring arm64 supported as Tier 3 [s] for OpenEmbedded using Yocto Honister (version 3.4.3, bitbake branch 1.52). Honister has only support for 7 months since its release (until May 2022) , but those are my client’s requirements.
Provided that I have enough time, I plan to validate things for arm64. I’m currently looking for beta testers and volunteers that:
validate the Yocto recipes in arm32
bring the recipes to Kirkstone Yocto release
If there’s no community interest on arm32, we should downgrade the support level and mark only arm64 support. Similarly, it might be a good idea to annotate REP-2000 with the Yocto release that’s being supported.