Downstream Zephyr RTOS Release Management - Keeping up With Upstream Pace
Talkat Open Source Summit India 2026 · on Tuesday, 2026-06-16· at 16:50· Lotus Ballroom 2 (Level 3)·
summary
Zephyr reaches ten years with ~3,000 contributors, ~150k commits and ~15k commits per release, and downstream teams face fast upstream churn: 17,000 PRs in one year and ~50%+ of kernel/driver C code merged with no C review. Tooling constraints cause Python dependency drift, DTS and binding breakage and runtime faults; release cadence centers on SDK, West and Twister but lacks wide hardware CI, so teams build LabVia-style remote hardware labs and use a track-and-rebase vs backport strategy.
AI-written summary · about
chapters (11)
- 0:00Zephyr downstream release intro
- 3:55Upstream release cycles
- 10:37Ecosystem and SDK deps
- 15:20Challenges migrating releases
- 19:34Downstream management approaches
- 23:01Code review gaps impact
- 26:56Release strategy and patches
- 31:08Hardware testing in dev
- 36:01AI and human review role
- 37:26Community contributions feedback
- 40:35Q&A
related talks
42mTaking Your Hardware to Production with Zephyr RTOS
33mContinues Integration Practices for Zephyr Upstream
10mLightning Talk: Using Zephyr to Power the Sustainable Cloud
33mContinues Integration Practices for Zephyr Upstream
21mKeynote: The Kernel Report
32mLeveraging Cloud Technologies for Development and Operation of Zephyr
08mHow we move code at ZenDesk
37mManifests: Project Sanity in the Ever-Changing Zephyr World