ROS PMC Minutes for April 8, 2025

[mjcarroll]

The ROS PMC meeting for this week was on Tuesday. The notes from the meeting are available at ROS PMC weekly meeting agenda, April 8

PMC Business

• Formal Decision: End-of-life date for ROS Noetic (ROS Project Charter - article 4.9.v)

  • @sloretz proposes that May 31, 2025 is the official end-of-life date for ROS Noetic to coincide with the end-of-life date for Ubuntu Focal.
  • While not under the formal decision, for reference, the remaining Noetic schedule:
    • May 13 - Begin Sync Freeze
    • May 15th
      • Perform second to last Sync
      • Merge Noetic ros/rosdistro PRs
    • May 16th
      • Merge Noetic ros/rosdistro PRs
      • Begin final sync freeze
    • May 16th - May 29th
      • Only accept Noetic ros/rosdistro PRs that fix regression
    • May 29th Perform last sync
    • @sloretz to post on Discourse official decision and schedule
    • @kscottz moved, @Yadunund second, passed by consensus

• Formal Decision: Add rmw_zenoh to REP 2005 (ROS Project Charter - article 4.9.ii)

  • @Yadunund proposes adding rmw_zenoh to maintained repositories under the ROS PMC: Add rmw_zenoh to REP 2005 by mjcarroll · Pull Request #417 · ros-infrastructure/rep · GitHub
  • @ahcorde moved, @Yadunund seconded, passed by consensus

Ongoing Tasks

• Buildfarm:
  • Planned build.ros2 repo agent migration for next Tuesday
• Waffle assignments:
  • April 10 + April 17: @sloretz
• Rosdistro Assignments
  • April 8 - April 15: @wjwwood + @marcogg
• Outgoing rosdistro issues:
  • @sloretz: How do we handle python dependency groups?
    • Context: Add python3-jraph-pip by stergiosba · Pull Request #44942 · ros/rosdistro · GitHub
    • Conclusion: rosdep doesn’t support this, and probably won’t with some additional feature development. For now, we can use dependency-specific keys like jax-nvidia to differentiate from jax
  • @sloretz We are in scheduled brown-outs on our current github runner, and need to update:
    • Use ubuntu-latest runner Try making Build & Test action use ubuntu latest by sloretz · Pull Request #45033 · ros/rosdistro · GitHub
• ROS Bosses:
  • Shane (Noetic)
    • Noetic Sync finishing today
    • Make many Noetic releases after the sync
  • Marco (Jazzy)
    • New packages and patch release 4 for Jazzy Jalisco 2025-04-07
    • @mjcarroll to post about Executor ABI break
  • Yadu (Rolling)
    • Rolling sync on Friday

Kilted Development

• rmw_zenoh
  • All RMW freeze PRs merged
  • Next focus: getting infrastructure support for the router and isolation + reverting multicast PRs.
• FastDDS
  • All RMW freeze PRs merged
• Connext
  • All RMW freeze PRs merged
  • Note that Windows buildfarm only supports 7.3 at the moment, so there may be regressions in Humble and Jazzy Windows builds until the end of the week.
• Action Introspection
  • Iterating on rosbag2 pull request with @MichaelOrlov

Agenda Items

• [@cottsay] Kilted Release Timeline
  • We’re now in the RMW Feature Freeze period
    • We had some late-breaking changes which regressed linters and such, will follow-up with fixes for those soon.
  • On Monday (4/14), we will enter the ROS 2 Core Feature Freeze
    • Bug fixes only for core packages after that
    • Please tag me (@cottsay) on all PRs to Rolling for core packages. You don’t need my review, I just want to make sure I get the notification.
  • From here until release, we’ll be hitting milestones (at least) every Monday. Have a look at the timeline for details.
• [@mjcarroll] ROSCon Key Dates
  • Diversity Scholarship - April 18, 2025
  • Workshop proposals - May 5, 2025
  • Talk proposals - June 2, 2025
  • Acceptance - July 14, 2025
  • ROSCon - October 27, 2025
• [@emersonknapp] Difference between demos/examples?
  • How does this repository differ from ros2/demos? · Issue #406 · ros2/examples · GitHub
  • Conclusion: Emerson to make a proposal around what each repo should look like and the sequence of moves to get us there in the above issue. We can use this to align/agree.
• [@nuclearsandwich] ROS repository keys
  • On May 31, rosdistro repository keys will rotate again.
  • By May 31, we want to have converted all active ROS installations to using a new ros-archive-keyring package that distributes both the public signing key and the repository configuration in place of our current installation instructions.

As a reminder, ROS PMC meetings are open to the public, though only committers and members may speak without being called on. If you have topics that you would like discussed, feel free to respond here.