Skip to content

Project Roadmap

Jump to bottom
Rob Woolley edited this page Jan 19, 2026 · 1 revision

Here are draft plans for the ROS OpenEmbedded Community in 2026:

Golden Releases

  • Focus on Scarthgap and Jazzy LTS for production
  • Rolling on master for development
  • Sunset Kirkstone in April 2026
  • Maintain all supported Yocto and ROS 2 combinations and machines
  • Getting started instructions and bitbake-setup configurations
  • Documentation on validated tools and versions (eg. Rocker and ROS VSCode extension)

Formal release process

  • Define versioning
  • Automated tests with test report (incl. ptest, testimage, and ament_cmake_test)
  • Add release notes with changelogs
  • Provide information on SBOMs and provenance (signed tags / artifacts)
  • Publish an artifact policy (types, signatures, reproducibility checklist, retention)
  • Frame expectations (best-effort, community-level support)

Pre-built images

  • Focus on most common use cases with fully-integrated images
  • Machines: genericx86-64, raspberrypi5, beaglev-fire (Space ROS)
  • Paired with downloadable SDKs and Devcontainers
  • Tuned for performance and size (eg. RT, amdv3, etc)
  • Quick start image (desktop images: RPi5 or QEMU amd64 VMs)
  • OE ROS Containers
  • Launch ROS running natively on workstation for quick prototyping

Tooling

Demos

  • Space ROS demos
    • Canadarm2 and Mars Curiosity Rover
  • CARLA integration
  • Autoware / Open AD Kit exploration
  • micro-ROS / MCU demo
  • PX4 + ROS 2 bridge demo
  • AGL SoDeV

Hosting infrastructure

  • Find cost-efficient hosting solution
  • Containers
  • GitHub Container Registry (GHCR)
  • Docker Hub?
  • Filesystem images & SDKs:
  • Cloudflare R2 ($0.015/GB-month with no egress fees) https://developers.cloudflare.com/sponsorships/ ?
  • GitHub Releases?
  • Binary package feeds
  • What package format? (ipk / rpm / deb)?
  • What are the public facing use cases for packages? Would custom container images be preferred?

Clone this wiki locally