Apache Druid vs Fulcrum

The feed alternates release-candidate tags with the majors they become: 35.0.1 in December, 36.0.0 in February, 37.0.0 in May. The majors are big and diffuse — 37.0.0 counts over 255 changes from 29 contributors, 36.0.0 over 189 from 34 — and are summarised by contributor counts and pointers to upgrade notes rather than headline features. The one patch in the window fixed segment-drop file descriptors leaking until process exit, which is the kind of detail that tells you who runs this: operators with long-lived clusters.

This is a mature Apache project on a predictable cadence, where each release aggregates hundreds of contributions instead of pursuing a theme. Every major carries explicit incompatible-changes and upgrade notes, so compatibility management is treated as a first-class part of shipping. Nothing in the feed points toward a directional shift; the signal is steadiness.

On this cadence the next major and its release candidate are due within a quarter of 37.0.0, likely with a similar volume of changes. What those changes contain cannot be inferred — the entries deliberately defer detail to the linked notes.