PX4 Dev Call: Aug 05, 2026 (Team sync, and Community Q&A)

PX4 Sync / Q&A - 2026-08-05T15:00:00Z

This week: 33 PRs merged | 266 awaiting review | 0 new bugs


Announcements


  1. MAVLINK- Hackathon happened last week (Will add YT videos and blog posts here)
  2. PX4 Dev summit schedule is live OSS + ELC EU 2026: Schedule For PX4 Dev Summit Events @ Prague, Czechia (Hobbyists can apply
  3. We are setting up a security WG, talking with couple different research groups. The discussion is what is falling into security category vs bugs. Considerable amount of documentation and discussion of course needed to have this up and running.

Events


Dev Call Items

  • Flight testing
  • Release

Release

Updates:

  • Flight test team is going to test v1.18 beta soon .
  • There is a list of bug fixes added to main recently which are worth backported to v1.18.

Issues:

Decisions:

  • Expecting beta2 to be cut soon so the flight tests could be don on that.

PRs Merged This Week

33 PRs merged this week →

  1. fix(drivers/invensense): use exact 20-bit gyro scale factors by dakejahl · Pull Request #28133 · PX4/PX4-Autopilot · GitHub
  2. fix(drivers/invensense): always publish full-scale FIFO data by dakejahl · Pull Request #28134 · PX4/PX4-Autopilot · GitHub
  3. feat(control_allocator): reversible-motor failure recovery for hexarotors by gguidone · Pull Request #28078 · PX4/PX4-Autopilot · GitHub (This is very interesting if come in)

PRs Awaiting Review

266 PRs awaiting review →


New Bug Reports

  • No new bugs

Other New Issues

5 new issues →


Q&A


  1. How does the backport work? Ans: We recommend to backport one version back only if there is a critical bug.
  2. Is there something like LTS in PX4 as there are for Ubuntu for example? Ans: Based on the large regressions, it is not recommended to do backports or make changes more than a version back. There are plans to bring an LTS release cycle maybe a long time from now which needs proper support and funding and dedicated people as LTS mangers.

Action Items