Sulu
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
A side-by-side editorial comparison of Joomla and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Three release lines in parallel, and changelogs that publish checksums instead of changes
Joomla is running three lines at once: 5.4.x maintenance, 6.1.x stable, and a 6.2 alpha. The GitHub release feed is the only signal captured here and it carries no feature detail — every entry repeats the same template of contributor counts, merged-PR counts, download links and SHA-256 checksums, with user-facing notes deferred to an off-site release page. Volume is the only thing that distinguishes them: 5.4.7 merged 43+ pull requests where the 6.1.2 candidates carry one apiece.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
Joomla is running three lines at once: 5.4.x maintenance, 6.1.x stable, and a 6.2 alpha. The GitHub release feed is the only signal captured here and it carries no feature detail — every entry repeats the same template of contributor counts, merged-PR counts, download links and SHA-256 checksums, with user-facing notes deferred to an off-site release page. Volume is the only thing that distinguishes them: 5.4.7 merged 43+ pull requests where the 6.1.2 candidates carry one apiece.
The pattern is a CMS mid-transition, keeping the 5.x line on a heavy maintenance drip while 6.1 stabilises and 6.2 opens in alpha. Every release links a new migration guide and new developer documentation, which suggests the 5-to-6 upgrade path remains the project's central concern. Where the capability surface is heading isn't determinable from this feed — that information simply isn't published in it.
Expect continued parallel maintenance on 5.4.x and 6.1.x with 6.2 progressing through further alphas; the entries give no basis for calling what 6.2 will actually contain.
Pimcore maintains two calendar-versioned lines in parallel, 2026.2.x and 2026.1.x, with fixes landing on the newer line and selectively backported. The content is dominated by input-validation work: explicit field allowlists on Custom Report updates, an ORDER BY column allowlist for redirect listings, rejection of unwhitelisted filter properties, escaped field names in DataObject JOIN conditions, hardened unserialize paths, and CSV exports bound to the requesting user. Feature work is thin by comparison — a CDN integration and a TemplateProviderInterface extension point in 2026.2.1.
The pattern is a systematic pass over places where user input reaches SQL or deserialization, spread across releases rather than bundled into one advisory — Custom Reports alone are touched in three separate releases. Alongside it runs a slower cleanup of the v11 era: admin functions removed, admin translations deprecated, v11-specific workflows refactored to v12. A task in the most recent release adds backward-compatibility break detection to the project's own code review tooling, which reads as an attempt to keep that cleanup from breaking integrators unannounced.
Expect the hardening sweep to keep producing small paired releases on both lines, with Custom Reports and listing filters the likely remaining targets, and further admin-layer removals as the v12 cleanup continues.
Other Mkt Auto 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 Joomla or Pimcore.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Measurement gets granular while the API quietly opens ClickFunnels up to outside agents
n8n's daily patch train hides the real work: hardening its MCP server into a proper auth resource.
OneSignal is arguing a new category into existence before showing the product behind it.
See all Joomla alternatives → · See all Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Joomla and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Joomla and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Joomla alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Joomla alternatives" section above for the current picks, or visit /alternatives/joomla for the full list with editorial commentary on each.
Top Pimcore alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pimcore alternatives" section above for the current picks, or visit /alternatives/pimcore for the full list with editorial commentary on each.