Support ROS 2 Jazzy Jalisco

[xmfcx]

Continuing from the discussion:

• Support ROS 2 Jazzy Jalisco #4893

Related Issues:

• Support ROS 2 Jazzy Jalisco autoware_universe#7598
• Support ROS 2 Jazzy autoware_core#623
• Support ROS 2 Jazzy autoware_universe#11418
• Support ROS 2 Jazzy autoware_tools#344
• Nebula support for Jazzy and other required updates for 0.3.* #6756
• Add build-and-test-differential checks for ROS 2 Jazzy as well autoware_tools#375

Transition Timeline

• From: Ubuntu 22.04 | ROS 2 Humble
• To: Ubuntu 24.04 | ROS 2 Jazzy

timeline
    title ROS 2 Humble to Jazzy Transition
    Feb 2026 : Jazzy Docker Beta
             : Optional CI Checks
    Apr 2026 : Jazzy Full Support
             : Dual CI Coverage
    Jan 2027 : Humble Soft-Freeze
             : Standard Support Ends
    May 2027 : Jazzy Exclusive Mode
             : Humble End of Support

Loading

gantt
    title ROS 2 Transition: Humble to Jazzy
    dateFormat  YYYY-MM-DD
    axisFormat  %b '%y
    tickInterval 1month

    %% Define Milestones (Vertical markers for key dates)
    section Key Events
    Jazzy Docker Beta       :milestone, m1, 2026-02-01, 0d
    Jazzy Full Support    :milestone, m2, 2026-04-01, 0d
    Humble Soft-Freeze      :milestone, m3, 2027-01-01, 0d
    Jazzy Exclusive         :milestone, m4, 2027-05-01, 0d

    %% Section 1: The Outgoing Platform
    section ROS 2 Humble
    Standard Support        :active,    h_std,  2026-01-01, 2027-01-01
    Low Maintenance (Crit Fixes) :crit, h_low,  after h_std, 2027-05-01
    End of Support          :done,      h_end,  after h_low, 1d

    %% Section 2: The Incoming Platform
    section ROS 2 Jazzy
    Docker Base Preview     :           j_beta, 2026-02-01, 2026-04-01
    Full Support (Ubuntu 24.04) :active, j_std,  after j_beta, 2027-06-01

    %% Section 3: Developer Action Items
    section CI Policy
    Optional Checks:           ci_opt, 2026-02-01, 2026-04-01
    Mandatory Dual Coverage :crit,      ci_man, 2026-04-01, 2027-05-01
    Jazzy Only              :active,    ci_jaz, after ci_man, 2027-06-01

    section Dummy Space For Github Renderer
    ‎ : ci_opt, 2026-01-01, 2026-01-01
    ‎ : ci_opt, 2026-01-01, 2026-01-01
    ‎ : ci_opt, 2026-01-01, 2026-01-01
    ‎ : ci_opt, 2026-01-01, 2026-01-01
    ‎ : ci_opt, 2026-01-01, 2026-01-01

Loading

[felixfeixu]

it should be possible, not that difficult, because I already have a local version running on ros2 Jazzy.

I think the key question is whether autoware (the team) have decided to move to Jazzy or not, are they open to review PRs if one is only to add support for Jazzy.

Moving to ROS2 Jazzy is also coupled with another issue, upgrade OS version or not (for example, Ubuntu 22 to Ubuntu 24?), some c++ library changed their cmake linkage method on Ubuntu 24.

Another minor issue is to upgrade gcc version or not. Some header files are mandatory for explicit inclusion in latest gcc version but can be ignore in older gcc version.

Last issue, we might do some code cleaning at the same time as well, and usually it's related to several different autoware repo, like autowarefoundation/autoware_core#646, never got reviewed (only AI reviewed it).

[xmfcx]

I will push for a transition timeline for this Tuesday.

Please link and ping @mitsudome-r and @xmfcx for unreviewed PRs.

For core, a docker version was made but for universe it is not made yet.
Right now the autoware dockerfile is too complex due to multicontainer stuff so it is making it harder to make a jazzy version.

And it makes it harder to add required CI for jazzy.

@mitsudome-r will move the multi container stuff to open ad kit repository so it will be maintained outside soon and şt will be much easier to add jazzy support then.

For the transition, we will have a period where we support both humble and jazzy at the same time. Then eventually drop humble support.