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 Gravity Forms and Liquidsoap — release velocity, themes, recent moves, and the top alternatives to consider.
Gravity Forms shipped 3.0 with accessibility on by default, then went back to add-on maintenance.
The 3.0 release is the substantive event in this window: international phone formatting with real validation, and accessibility settings enabled by default on new forms. Everything since has been add-on maintenance — Dropbox, Trello, Conversational Forms, and a Gravity Flow checklists extension all took point releases in a single batch — capped by a summer pricing promotion. The core plugin and its add-on ecosystem move on separate clocks, and the ecosystem clock is the one ticking right now.
Liquidsoap spent the whole 2.4 line paying down the cost of its own rewrite
Liquidsoap is a scripting language and runtime for building audio and video streams. The 2.4 series has been almost entirely stabilization: five patch releases since November 2025, two of them shipped within days of each other because the preceding one broke source cleanup, and 2.4.4 arriving with an explicit recommendation to skip 2.4.3. The recurring subject matter is clocks, source lifecycle and resource leaks — sub-clock leaks, crossfade crashes when skip is called off-thread, encoder sharing, Strings.Mutable leaks.
The 3.0 release is the substantive event in this window: international phone formatting with real validation, and accessibility settings enabled by default on new forms. Everything since has been add-on maintenance — Dropbox, Trello, Conversational Forms, and a Gravity Flow checklists extension all took point releases in a single batch — capped by a summer pricing promotion. The core plugin and its add-on ecosystem move on separate clocks, and the ecosystem clock is the one ticking right now.
Accessibility-by-default is the direction that matters. Turning it on for all new forms rather than leaving it an opt-in setting moves compliance from something a site builder has to know about to something they get automatically, and it is the kind of decision that is hard to walk back. The add-on releases suggest the post-3.0 phase is compatibility work across the integration catalog rather than new core capability.
Expect continued add-on point releases bringing integrations in line with 3.0 rather than new core features, since four add-ons shipped on the same day immediately after the major version. Accessibility defaults are the likely template for future settings that currently ship off.
Liquidsoap is a scripting language and runtime for building audio and video streams. The 2.4 series has been almost entirely stabilization: five patch releases since November 2025, two of them shipped within days of each other because the preceding one broke source cleanup, and 2.4.4 arriving with an explicit recommendation to skip 2.4.3. The recurring subject matter is clocks, source lifecycle and resource leaks — sub-clock leaks, crossfade crashes when skip is called off-thread, encoder sharing, Strings.Mutable leaks.
The project said outright at 2.4.1 that the internal rewrite and feature work were done and that effort would shift to stability, and the release record since then matches that claim. What new surface has appeared is diagnostic or defensive rather than expansive: clock and source graph pretty-printing, telnet commands for queue and output control, and raw string literals that stop interpolation from executing untrusted input. Performance work has targeted the same subsystem as the bugs, with clock sync-source propagation moving from a full scan to push-based updates.
The 2.4.3 notes state that 2.4.x was meant to end there and that 2.5.x work has begun, yet two more patches have shipped since — so the branch is likely to keep absorbing clock and source fixes until 2.5 lands. The notes give no date for it.
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 Gravity Forms or Liquidsoap.
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
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
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
See all Gravity Forms alternatives → · See all Liquidsoap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Gravity Forms alternatives in DevOps are ranked by recent ship velocity. Browse the "Gravity Forms alternatives" section above for the current picks, or visit /alternatives/gravity-forms for the full list with editorial commentary on each.
Top Liquidsoap alternatives in DevOps are ranked by recent ship velocity. Browse the "Liquidsoap alternatives" section above for the current picks, or visit /alternatives/liquidsoap for the full list with editorial commentary on each.