New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition Rolling to Ubuntu 22.04 #1221
Comments
|
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/preparing-ros-2-rolling-for-the-transition-to-ubuntu-22-04/23124/1 |
|
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-2021-11-18/23209/1 |
|
What is the latest (rough) timeline for this? The original discourse post talked about end of January, is this going to end up happening closer to the Humble release? |
Still shooting for the end of January. Given the work we had to do, this may end up slipping into the first week of February, but likely no longer than that. |
|
Thanks Chris, I just realized I was looking at the Dec notes, not Jan, where this was all written up. https://discourse.ros.org/t/ros-2-tsc-meeting-january-20th-2022/23986 |
|
I opened this issue and completely forgot to update it as I went. Some bootstrapping challenges with the Jammy debug job have arisen and devel jobs can't run without binary jobs at the foundation so the last several tasks will all tick over to Jammy in a short fell swoop. |
|
@nuclearsandwich Can we close this one out now? |
|
Rolling is well and truly on Jammy now (despite some lingering jobs left on Focal). As such, I'm going to close this out, but feel free to reopen if this issue is still needed. |
Continuing from the broad announcement on Discourse. Here's a detailed checklist of items to take care of for the Rolling transition to Ubuntu 22.04.
jammyandbullseyejammyandbullseyePrepare a Nightly Ubuntu Jammy debug build for the ROS 2 build farm in ros2/ros_buildfarm_configThe text was updated successfully, but these errors were encountered: