Hi all,
Following up on yesterday’s dev call: we’re moving forward with v1.18, on an accelerated schedule.
Deadlines
- Wednesday, June 24 - submit any PR you want in v1.18. Get it up early so there’s time for review and changes.
- Friday, June 26 - the
v1.18release branch freezes/cuts frommain.
Mark your PR for the release. An open PR does not automatically make it into 1.18. If you want it considered, add it to the v1.18 project board. We’ll be reviewing every PR on the board, so that’s how you get in the queue. If you’ve reached out to me about a PR recently and I haven’t replied yet, this is the step that counts: get it on the board.
The deadline is firm - we’re not moving it. The earlier you submit, the safer you are: if a reviewer asks for a change, you want time to make it before the 26th.
After the cut: only bug fixes and security fixes go on the v1.18 branch. Everything else continues on main. Then comes release testing - real flight testing by the Dronecode flight test team across multiple hardware boards and vehicle types (multicopter, fixed-wing, VTOL, rover, and more), not just CI and SITL. Plan on roughly 3-4 months to finalize.
Why the rush - the good news: we’re accelerating 1.18 because we’re already planning PX4 v2.0, and it’s a big one. On top of everything landing in this merge window, v2.0 takes on a major build system overhaul and the kind of foundational work we’ve wanted to tackle for years. Getting 1.18 into testing now gives us the runway to build 2.0 right, in parallel, without cutting corners. We’ll share more on v2.0 and how to get involved as it firms up - if it might touch your downstream, start thinking about how it reaches you.
Flight Testing Tracker: [v1.18 Release Candidate] - Flight Testing & Flight Issues (log archive) · Issue #27470 · PX4/PX4-Autopilot · GitHub
Project board: PX4 v1.18 Release · GitHub
Questions? Drop them below.
-Ramón