# Branched Humble + Call for Beta Testing

**URL:** <https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284>\
**Category:** ROS General\
**Tags:** release, ros2, humble\
**Created:** [April 26, 2022, 4:08pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284 "2022-04-26T16:08:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![audrow](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/audrow/32/4677_2.png) [@audrow](https://discourse.openrobotics.org/u/audrow)\
**Post date:** [April 26, 2022, 4:08pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/1 "2022-04-26T16:08:44Z")

</div>

We have branched Humble from Rolling! This means that (1) Rolling is now unfrozen, and that (2) we’ve entered the [“beta” testing phase](https://docs.ros.org/en/rolling/Releases/Release-Humble-Hawksbill.html#id25) of the Humble Release.

## Unfreezing Rolling

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](https://docs.ros.org/en/humble/Installation.html). 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:

1. Think about what package is most likely at fault and find its repository.
2. Check the repository for an issue or PR that describes or fixes the bug you’re seeing.
3. 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](https://docs.ros.org/en/humble/How-To-Guides/Releasing-a-ROS-2-package-with-bloom.html). For Humble, the minimum required version of bloom is 0.11.0.

---

<div class="post-metadata">

**Author:** ![dfarning](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/dfarning/32/11850_2.png) [@dfarning](https://discourse.openrobotics.org/u/dfarning)\
**Post date:** [April 27, 2022, 6:57pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/2 "2022-04-27T18:57:20Z")

</div>

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](http://packages.ros.org/ros2/ubuntu) jammy The name of the ros\* packages all still seem to be ros-rolling-\* for the current beta.

Am I doing something wrong or is the name still something that needs to be changed on the build system. On [ROS 2 Humble Hawksbill (codename ‘humble’; May, 2022) — ROS 2 Documentation: Foxy documentation](https://docs.ros.org/en/foxy/Releases/Release-Humble-Hawksbill.html#release-timeline) it states that the name should have been updated as of April 18, 2022.

This is my first-time beta testing a new release so I might be completely confused about how ros betas work.

---

<div class="post-metadata">

**Author:** ![clalancette](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/clalancette/32/4797_2.png) [@clalancette](https://discourse.openrobotics.org/u/clalancette)\
**Post date:** [April 27, 2022, 7:26pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/3 "2022-04-27T19:26:55Z")

</div>

Did you follow the instructions at [Ubuntu-Install-Debians — ROS 2 Documentation: Humble documentation](https://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html) ? In particular, you need to use [https://packages.ros.org/ros2-testing/ubuntu](https://packages.ros.org/ros2-testing/ubuntu) (note the extra `-testing` in there), since this is a still a distribution that is being tested out.

---

<div class="post-metadata">

**Author:** ![JanStaschulat](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/janstaschulat/32/16498_2.png) [@JanStaschulat](https://discourse.openrobotics.org/u/JanStaschulat)\
**Post date:** [April 28, 2022, 2:01pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/4 "2022-04-28T14:01:36Z")

</div>

Hi,  
I created a humble branch for the [rclc repository](https://github.com/ros2/rclc/tree/humble) today and updated the ros distribution name to ‘humble’ in the the [Github Action ci-job](https://github.com/ros2/rclc/blob/humble/.github/workflows/ci.yml). It fails when processing the step `ros-tooling/setup-ros@0.3.0` with the error message [Input has invalid distribution names.](https://github.com/ros2/rclc/runs/6206093760?check_suite_focus=true). For the time being, I reverted the ros-distribution name to ‘rolling’.

In the ci-job the option [use-ros2-testing: true](https://github.com/ros2/rclc/blob/5b87dcafe343a94d78f893a83a0a6290f63c83b5/.github/workflows/ci.yml#L29) is set, so I suppose, that packages are downloaded from [https://packages.ros.org/ros2-testing/ubuntu](https://packages.ros.org/ros2-testing/ubuntu)

Any suggestions, how to update the ci-job for humble? Or should I just wait until the official release in May?

---

<div class="post-metadata">

**Author:** ![christophebedard](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophebedard/32/1514_2.png) [@christophebedard](https://discourse.openrobotics.org/u/christophebedard)\
**Post date:** [April 28, 2022, 2:05pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/5 "2022-04-28T14:05:01Z")

</div>

I’ve opened issues to add support for Humble to the `setup-ros` and `action-ros-ci` GitHub actions:

- [Add support for Humble Hawksbill (May 2022) · Issue #483 · ros-tooling/setup-ros · GitHub](https://github.com/ros-tooling/setup-ros/issues/483)
- [Add support for Humble Hawksbill (May 2022) · Issue #738 · ros-tooling/action-ros-ci · GitHub](https://github.com/ros-tooling/action-ros-ci/issues/738)

You’ll indeed need to use the testing repository for now, but the actions are not currently aware that Humble is a (valid) distro. I’ll try to do it this weekend.

---

<div class="post-metadata">

**Author:** ![rosterloh](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/rosterloh/32/3985_2.png) [@rosterloh](https://discourse.openrobotics.org/u/rosterloh)\
**Post date:** [April 29, 2022, 8:48am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/6 "2022-04-29T08:48:52Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![vmayoral](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/vmayoral/32/3665_2.png) [@vmayoral](https://discourse.openrobotics.org/u/vmayoral)\
**Post date:** [April 29, 2022, 9:47am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/7 "2022-04-29T09:47:13Z")

</div>

Debian’s marked as `Tier 3 [s]`. Refer to [REP 2000 -- ROS 2 Releases and Target Platforms (ROS.org)](https://ros.org/reps/rep-2000.html#support-tiers:)

> Tier 3
> 
> 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.

and [REP 2000 -- ROS 2 Releases and Target Platforms (ROS.org)](https://ros.org/reps/rep-2000.html#humble-hawksbill-may-2022-may-2027:)

> " [s] " Compilation from source.

In other words, you’re welcome to build it from source. Many have expressed interest on getting Debian to a better stage of support, but resources need to be committed for that.

---

<div class="post-metadata">

**Author:** ![vmayoral](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/vmayoral/32/3665_2.png) [@vmayoral](https://discourse.openrobotics.org/u/vmayoral)\
**Post date:** [April 29, 2022, 10:13am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/8 "2022-04-29T10:13:48Z")

</div>

OpenEmbedded support is marked as `Tier 3 [s]`:

> | Architecture | Ubuntu Jammy (22.04) | Windows 10 (VS2019) | RHEL 8 | Ubuntu Focal (20.04) | macOS | Debian Bullseye (11) | OpenEmbedded / webOS OSE |
> | --- | --- | --- | --- | --- | --- | --- | --- |
> | amd64 | Tier 1 [d][a][s] | Tier 1 [a][s] | Tier 2 [d][a][s] | Tier 3 [s] | Tier 3 [s] | Tier 3 [s] | |
> | arm64 | Tier 1 [d][a][s] | | | Tier 3 [s] | | Tier 3 [s] | Tier 3 [s] |
> | arm32 | Tier 3 [s] | | | Tier 3 [s] | | Tier 3 [s] | Tier 3 [s] |

I’m currently working on a [branch](https://github.com/vmayoral/meta-ros/tree/honister-humble) (⚠ _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.

---

<div class="post-metadata">

**Author:** ![vmayoral](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/vmayoral/32/3665_2.png) [@vmayoral](https://discourse.openrobotics.org/u/vmayoral)\
**Post date:** [April 29, 2022, 10:20am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/9 "2022-04-29T10:20:17Z")

</div>

> [@vmayoral](#):
>
> 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.

@robwoolley, any chance you’re interested to help in any of these things? Are you currently planning any other contributions towards `Humble` for OpenEmbedded support?

---

<div class="post-metadata">

**Author:** ![rosterloh](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/rosterloh/32/3985_2.png) [@rosterloh](https://discourse.openrobotics.org/u/rosterloh)\
**Post date:** [April 29, 2022, 10:23am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/10 "2022-04-29T10:23:12Z")

</div>

@vmayoral that’s very clear thank you. I’d be happy to test and contribute to OE build and testing. I’ve worked on jobs like this before.

---

<div class="post-metadata">

**Author:** ![vmayoral](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/vmayoral/32/3665_2.png) [@vmayoral](https://discourse.openrobotics.org/u/vmayoral)\
**Post date:** [April 29, 2022, 10:40am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/11 "2022-04-29T10:40:25Z")

</div>

> [@rosterloh](#):
>
> I’d be happy to test and contribute to OE build and testing. I’ve worked on jobs like this before.

That’s be fantastic, thanks. If you have cycles, feel free to start testing things out of [ROS 2 Humble Hawksbill - honister branch by vmayoral · Pull Request #1003 · ros/meta-ros · GitHub](https://github.com/ros/meta-ros/pull/1003) and provide your feedback. PRs are welcome as well against my dev. branch. If you’d like to sign up as beta tester, say so in that ticket directly with your GitHub username please.

---

<div class="post-metadata">

**Author:** ![dfarning](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/dfarning/32/11850_2.png) [@dfarning](https://discourse.openrobotics.org/u/dfarning)\
**Post date:** [May 2, 2022, 1:14pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/12 "2022-05-02T13:14:58Z")

</div>

What is the etiquette for requesting ROS Humble branches and builds from third-party packages when doing Beta testing?

Is it okay to open issues on the package’s Github repository or should I wait until humble has been officially released?

---

<div class="post-metadata">

**Author:** ![clalancette](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/clalancette/32/4797_2.png) [@clalancette](https://discourse.openrobotics.org/u/clalancette)\
**Post date:** [May 2, 2022, 1:39pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/13 "2022-05-02T13:39:51Z")

</div>

I think it is reasonable to ask maintainers for a branch at this point. The Humble distribution is a viable target, so there are no blockers to moving forward.

That said, there is also no obligation for the maintainers to do so at this time, so please be patient 🙂 .

---

<div class="post-metadata">

**Author:** ![christophebedard](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophebedard/32/1514_2.png) [@christophebedard](https://discourse.openrobotics.org/u/christophebedard)\
**Post date:** [May 3, 2022, 1:25am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/14 "2022-05-03T01:25:57Z")

</div>

> [@christophebedard](#):
>
> I’ve opened issues to add support for Humble to the `setup-ros` and `action-ros-ci` GitHub actions:
> 
> - [Add support for Humble Hawksbill (May 2022) · Issue #483 · ros-tooling/setup-ros · GitHub](https://github.com/ros-tooling/setup-ros/issues/483)
> - [Add support for Humble Hawksbill (May 2022) · Issue #738 · ros-tooling/action-ros-ci · GitHub](https://github.com/ros-tooling/action-ros-ci/issues/738)

Just to follow up, `setup-ros` and `action-ros-ci` can now be used for Humble (with the testing repo for now).

---

<div class="post-metadata">

**Author:** ![Atharva\_Bhorpe](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/atharva_bhorpe/32/13338_2.png) [@Atharva\_Bhorpe](https://discourse.openrobotics.org/u/Atharva_Bhorpe)\
**Post date:** [May 4, 2022, 7:01am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/15 "2022-05-04T07:01:52Z")

</div>

I was installing micro-ros on ros2 humble beta, and using this command:

```auto
git clone -b $ROS_DISTRO https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup

```

I got this output:

```auto
Cloning into 'src/micro_ros_setup'...
fatal: Remote branch rolling not found in upstream origin

```

I guess there’s still a dependancy where the “ROS\_DISTRO” is set to “Rolling”.  
It’s not a big deal as Humble is derived from Rolling.

The work-around was to replace the “$ROS\_DISTRO” from the command with “humble”:

```auto
git clone -b humble https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup

```

P.S.- I didn’t know where else to post this, so please excuse this post, and point me to the right site/url.

---

<div class="post-metadata">

**Author:** ![clalancette](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/clalancette/32/4797_2.png) [@clalancette](https://discourse.openrobotics.org/u/clalancette)\
**Post date:** [May 4, 2022, 12:33pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/16 "2022-05-04T12:33:08Z")

</div>

> [@Atharva\_Bhorpe](#):
>
> I guess there’s still a dependancy where the “ROS\_DISTRO” is set to “Rolling”.

Good point. We have fixed this in the sources, but we haven’t done a release of that package yet. We’ll go ahead and do that. Thanks for the report.

---

<div class="post-metadata">

**Author:** ![JanStaschulat](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/janstaschulat/32/16498_2.png) [@JanStaschulat](https://discourse.openrobotics.org/u/JanStaschulat)\
**Post date:** [May 6, 2022, 9:42am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/17 "2022-05-06T09:42:15Z")

</div>

@christophebedard Thanks for updating the ros-tooling scripts. Our [ci-job for rclc on humble](https://github.com/ros2/rclc/pull/288) runs again.

However, with `os: [ubuntu-22.04]`, the [ci-pipeline fails already when initializing the container](https://github.com/ros2/rclc/runs/6320289481?check_suite_focus=true). As of now, I am using `ubuntu-20.04`.

---

<div class="post-metadata">

**Author:** ![JanStaschulat](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/janstaschulat/32/16498_2.png) [@JanStaschulat](https://discourse.openrobotics.org/u/JanStaschulat)\
**Post date:** [May 6, 2022, 9:51am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/18 "2022-05-06T09:51:15Z")

</div>

I opend a ticket here: [micro-ros release for humble · Issue #514 · micro-ROS/micro\_ros\_setup · GitHub](https://github.com/micro-ROS/micro_ros_setup/issues/514)

---

<div class="post-metadata">

**Author:** ![christophebedard](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophebedard/32/1514_2.png) [@christophebedard](https://discourse.openrobotics.org/u/christophebedard)\
**Post date:** [May 6, 2022, 1:56pm UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/19 "2022-05-06T13:56:08Z")

</div>

This seems to be due to an issue on the GitHub actions/infrastructure side. I’ve opened an issue to track this, let’s move the discussion there: [Unable to use Ubuntu 22.04 natively on GitHub actions · Issue #746 · ros-tooling/action-ros-ci · GitHub](https://github.com/ros-tooling/action-ros-ci/issues/746)

---

<div class="post-metadata">

**Author:** ![vmayoral](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/vmayoral/32/3665_2.png) [@vmayoral](https://discourse.openrobotics.org/u/vmayoral)\
**Post date:** [May 17, 2022, 11:47am UTC](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284/20 "2022-05-17T11:47:40Z")

</div>

@rosterloh changes in meta-ros for `Humble` in `Honister`’s Yocto release are ready for review: [ROS 2 Humble Hawksbill - honister branch by vmayoral · Pull Request #1003 · ros/meta-ros · GitHub](https://github.com/ros/meta-ros/pull/1003).

A short writeup about it is available at [ROS 2 Humble with Yocto and PetaLinux](https://news.accelerationrobotics.com/ros2-humble-yocto-petalinux/).

[Next page](https://discourse.openrobotics.org/t/branched-humble-call-for-beta-testing/25284.md?page=2)