DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
A side-by-side editorial comparison of Fission and Sonarr — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Sonarr is in pure maintenance mode — six releases, not one feature.
Six point releases in this window and none of them carries a feature. The changes are an ordering fix so free space is not checked when another specification has already failed, unexpected database language values normalized to Unknown, basic auth repaired for qBittorrent, and a Jellyfin and Emby connection test with a new Jellyfin auth header. One release ships with no changelog entry at all.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
Six point releases in this window and none of them carries a feature. The changes are an ordering fix so free space is not checked when another specification has already failed, unexpected database language values normalized to Unknown, basic auth repaired for qBittorrent, and a Jellyfin and Emby connection test with a new Jellyfin auth header. One release ships with no changelog entry at all.
This is a mature application on a stable branch, and the work is reactive: download clients and media servers change upstream, integrations break, Sonarr repairs them. The qBittorrent basic auth fix appearing on both the 4.0.18 and 4.0.19 lines shows a project deliberately keeping a maintenance branch alive rather than pushing everyone forward.
Nothing in these entries points to a feature cycle. Expect the same pattern — small point releases tracking upstream changes in download clients and media servers — to continue.
Other Infra & APIs 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 Fission or Sonarr.
DNSControl is rewriting its record internals in public, one release candidate at a time
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeePass-compatible password manager frozen mid-patch-run since 2021.
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all Fission alternatives → · See all Sonarr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sonarr is currently shipping more aggressively (velocity 5.0 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. Sonarr is currently shipping more aggressively (velocity 5.0 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 Infra & APIs products to evaluate alongside.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.
Top Sonarr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Sonarr alternatives" section above for the current picks, or visit /alternatives/sonarr for the full list with editorial commentary on each.