Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of bolasso and Strimzi — release velocity, themes, recent moves, and the top alternatives to consider.
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
The 1.2.0 release cycle has reached its second candidate, and it is a small one: a single fix for incorrect CA logging on top of rc1. Everything substantive in this release landed in rc1 — Kafka 4.3.1 support, per-pod volume templates, and server-side apply now permanently enabled. This feed publishes only release candidates and never the finals, so an rc is the record of what shipped.
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
The package spent 2022 dormant after its initial releases and has been actively developed since late 2024, moving from a single algorithm toward a workbench. The additions cluster around inspection rather than estimation: tidy() for bootstrap-level coefficients, plot_selection_thresholds() for selection stability across thresholds, plot_selected_variables() for the surviving covariates, and now the extracted bootstrap indices. Documented gaps remain, with mgaussian unsupported and multinomial prediction limited to class output.
The two stated limitations in 0.5.0 - no mgaussian family and class-only multinomial prediction - are the most likely next targets, since the maintainer flagged both as possible later additions.
The 1.2.0 release cycle has reached its second candidate, and it is a small one: a single fix for incorrect CA logging on top of rc1. Everything substantive in this release landed in rc1 — Kafka 4.3.1 support, per-pod volume templates, and server-side apply now permanently enabled. This feed publishes only release candidates and never the finals, so an rc is the record of what shipped.
Post-1.0 Strimzi is spending its cycles on how the operator manages Kubernetes resources rather than on new Kafka surface. ServerSideApplyPhase1 has gone alpha to GA and is now always on, and 1.2.0 changes install-time defaults toward Restricted Pod Security Standard security contexts and volume-mounted Service Account tokens. A second candidate carrying one logging fix says the cycle is converging rather than still absorbing change — the CRD v1-only requirement from 1.0.0 remains the loudest thing in every release body.
Expect 1.2.0 final shortly with no further candidates, and the next cycle to advance one of the open feature gates — UseBackgroundPodDeletion is the likeliest to move from alpha to beta.
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 bolasso or Strimzi.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
See all bolasso alternatives → · See all Strimzi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Strimzi 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. Strimzi 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 bolasso alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bolasso alternatives" section above for the current picks, or visit /alternatives/bolasso for the full list with editorial commentary on each.
Top Strimzi alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Strimzi alternatives" section above for the current picks, or visit /alternatives/strimzi for the full list with editorial commentary on each.