cockroachdb/cockroach

Prefer this fork only if you want the historical upstream state exactly and do not need current CockroachDB fixes or features. For most adopters, upstream is the better choice because this fork shows no added value and is extremely far behind.

Do not choose this fork for active production use unless you specifically want a frozen 2024 snapshot and are willing to own all future maintenance; active users should prefer upstream.

Prefer this fork only if you need an old, heavily modified CockroachDB baseline for experimentation or reproduction. For any production, upgrade-sensitive, or maintenance-heavy use, current upstream is the better choice because this fork is stale and materially behind.

Prefer upstream unless you specifically need the 2024 snapshot this fork preserves. This fork shows no added capabilities and is far behind upstream, so it is not a good adoption candidate for ongoing use.

Do not adopt this fork if you want a maintained database platform. It offers no visible value over upstream and is far behind on fixes and features; only choose it as a historical snapshot.

Prefer upstream unless you explicitly need the old 2023 snapshot. This fork adds no visible features, is heavily behind, and is best treated as an archival or personal reference copy rather than a maintained alternative.

Do not adopt this fork for product or operational use. It is a stale, documentation-only divergence from an active upstream and offers no evident functional advantages over upstream CockroachDB.

Prefer upstream unless you need an exact frozen snapshot from March 2023. This fork does not appear to add features or maintenance value, and its large distance from upstream makes it a poor adoption target for production or active development.

Prefer upstream unless you specifically need a frozen 2022-era snapshot; this fork offers no visible downstream enhancements and is too far behind for practical adoption.