Scalingo
Scalingo is back to routine runtime updates after its October router incident.
A side-by-side editorial comparison of Liquidsoap and Slurm — release velocity, themes, recent moves, and the top alternatives to consider.
Liquidsoap 2.5.0 reaches its first release candidate while 2.4 keeps getting patches.
Liquidsoap's 2.5.0 work, accumulated in a rolling release since August, reached a first release candidate on October 9, declared feature-complete and meant for staging rather than production. It brings subtitles as a content type, an Icecast-compatible server and a rewritten source composition model where switching fades by default. The 2.4 line continues in parallel: 2.4.6 on October 18 fixed fades, Icecast reconnection with chunked output and crossfade metadata.
Slurm's 26.05 line settles into routine fixes after September's seven-CVE release.
Slurm maintains three branches (25.05, 25.11, 26.05). On September 2 it shipped coordinated security releases on all three fixing seven CVEs, including an operator-to-administrator privilege escalation and SQL injection via cluster names. 26.05.5 on October 13 returned to ordinary fixes: qstat -f output, a slurmd double free and powered-down nodes placed incorrectly. 26.05.3 in August added external nodes in heterogeneous jobs.
Liquidsoap's 2.5.0 work, accumulated in a rolling release since August, reached a first release candidate on October 9, declared feature-complete and meant for staging rather than production. It brings subtitles as a content type, an Icecast-compatible server and a rewritten source composition model where switching fades by default. The 2.4 line continues in parallel: 2.4.6 on October 18 fixed fades, Icecast reconnection with chunked output and crossfade metadata.
The project is in the run-up to a breaking release: 2.5 changes how switch, fallback, rotate and random take their arguments, so scripts will need edits. Keeping 2.4 patched in parallel gives users time to test before moving.
Further 2.5.0 release candidates and then a 2.5.0 final are the next likely entries, with another 2.4.x patch possible alongside.
Slurm maintains three branches (25.05, 25.11, 26.05). On September 2 it shipped coordinated security releases on all three fixing seven CVEs, including an operator-to-administrator privilege escalation and SQL injection via cluster names. 26.05.5 on October 13 returned to ordinary fixes: qstat -f output, a slurmd double free and powered-down nodes placed incorrectly. 26.05.3 in August added external nodes in heterogeneous jobs.
The 26.05 line, which introduced SLUID identity and an in-tree TLS path in May, is past its security scramble and into routine point releases. Older branches get backports only when a security fix requires it.
Expect 26.05.6 on a similar monthly pace with reliability fixes; another coordinated security release would again cover all three branches.
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 Liquidsoap or Slurm.
Scalingo is back to routine runtime updates after its October router incident.
Mapnik 4.3.2 is a performance release from one contributor, with line dash fixes.
OpenJ9 0.63 patches CVEs and hardens JITServer against malformed messages.
OpenWrt's releases are still set by security fixes, now mostly on the 25.12 branch.
QGroundControl's v5.1.5 patch restores mission commands lost to a translation bug.
OSRM follows plaza routing with driving-side detection and turn costs against traffic.
See all Liquidsoap alternatives → · See all Slurm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap is currently shipping more aggressively (velocity 5.0 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. Liquidsoap is currently shipping more aggressively (velocity 5.0 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 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.
Top Slurm alternatives in DevOps are ranked by recent ship velocity. Browse the "Slurm alternatives" section above for the current picks, or visit /alternatives/slurm for the full list with editorial commentary on each.