Undertow
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
A side-by-side editorial comparison of OSQP and QGroundControl — release velocity, themes, recent moves, and the top alternatives to consider.
QP solver that rebuilt its linear algebra layer for GPUs, then went quiet in beta.
OSQP is an operator-splitting quadratic program solver used widely as an embedded optimization backend. Its visible release history stops at the v1.0 beta from May 2023, which was a substantial rework: a pluggable linear algebra backend chosen at compile time, the separate cuOSQP GPU project folded into the main tree, and an Intel MKL backend added. That beta has not been followed by a stable v1.0 in this feed.
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
QGroundControl shipped v5.0 in July 2025 after five release candidates, patched it through 5.0.8 in October, and then published nothing until a v5.1 release candidate at the end of July 2026. The v5.0 release was the substantive event: the Fly View toolbar, instrument selection, multi-vehicle telemetry and application settings were reworked, MAVLink 2 signing arrived, and the build system was converted entirely to cmake with qmake dropped. The patch line that followed was almost purely crash and platform fixes — Mac notarization, Android SD-card permissions for API 30+, parameter-loading crashes.
OSQP is an operator-splitting quadratic program solver used widely as an embedded optimization backend. Its visible release history stops at the v1.0 beta from May 2023, which was a substantial rework: a pluggable linear algebra backend chosen at compile time, the separate cuOSQP GPU project folded into the main tree, and an Intel MKL backend added. That beta has not been followed by a stable v1.0 in this feed.
The direction the beta set is clear — OSQP was becoming a solver core that could be retargeted at different compute hardware without changing the algorithm, with CUDA and MKL as the first two targets. Code generation and adjoint derivative computation moving into the C API point the same way, toward embedding OSQP inside other systems including differentiable pipelines.
The stable v1.0 is the obvious next milestone, but nothing in these entries indicates when or whether it landed — treat the backend rework as available only in beta form.
QGroundControl shipped v5.0 in July 2025 after five release candidates, patched it through 5.0.8 in October, and then published nothing until a v5.1 release candidate at the end of July 2026. The v5.0 release was the substantive event: the Fly View toolbar, instrument selection, multi-vehicle telemetry and application settings were reworked, MAVLink 2 signing arrived, and the build system was converted entirely to cmake with qmake dropped. The patch line that followed was almost purely crash and platform fixes — Mac notarization, Android SD-card permissions for API 30+, parameter-loading crashes.
The ten-month gap between 5.0.8 and the 5.1 candidate is the clearest signal in these entries: development moved off the release feed rather than stopping, since 5.1 arrives as an RC rather than a patch. The stated design intent from v5.0 — pushing flight-to-flight settings into the toolbar and reserving Vehicle Configuration for initial setup — is a durable direction, and the touch-screen focus points at integrated controllers like Herelink as the target hardware. The RC itself carries no changelog, deferring to an external What's New page.
A v5.1 stable release should follow within weeks of the candidate, and on the v5.0 precedent it will be followed by a run of 5.1.x patches concentrated on platform packaging and crash fixes rather than features.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either OSQP or QGroundControl.
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
Betaflight grew a real autopilot: waypoint missions, geofence RTH and MAVLink ground control
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
WildFly's quarterly train is really a stability ladder, and OIDC keeps climbing it
Jakarta REST implementation in pure maintenance across two parallel branches.
See all OSQP alternatives → · See all QGroundControl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. QGroundControl is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. QGroundControl is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top OSQP alternatives in DevOps are ranked by recent ship velocity. Browse the "OSQP alternatives" section above for the current picks, or visit /alternatives/osqp for the full list with editorial commentary on each.
Top QGroundControl alternatives in DevOps are ranked by recent ship velocity. Browse the "QGroundControl alternatives" section above for the current picks, or visit /alternatives/qgroundcontrol for the full list with editorial commentary on each.