Skip to content

docs(readme): 2026.10.8 vs 5.3.28 numbers, fork changes, how to contribute - #231

Merged
gburd merged 3 commits into
masterfrom
docs/readme-2026-10-8
Oct 30, 2026
Merged

gburd merged 3 commits into
masterfrom
docs/readme-2026-10-8

Conversation

@gburd

@gburd gburd commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

README for the v2026.10.8 release. The changes:

  • "Measured against Berkeley DB 5.3.28": v2026.10.8 ÷ 5.3.28 on one c6id.metal, for 11 key/value rows plus TPC-C-like and TPC-B-like. It says what is faster, what is about the same and what is still slower, and why. The source is the test/bench/XREL-2026-10.md addendum (bench: Berkeley DB 5.3.28 vs LTS 2026.10.7.1 vs master, every access method #227).
  • "What the fork has changed since 5.3.28": concurrency and performance, correctness and isolation, new features, portability, and release discipline. Each claim is taken from a release note or the qualification matrix.
  • Contributing:
    • how to report a bug, and what to include;
    • the private security route;
    • the PR steps;
    • what a performance claim needs;
    • where fixes land (master first, backport-lts for the LTS line).
  • RFCs: a "do I need one?" list.
  • The release table lists v2026.10.8 as the current regular release.
  • test/KNOWN-ISSUES.md gains I1: configure cannot guess the build type on Linux aarch64, because config.guess dates from 2011. It is present since v5.3.28, and the row gives the workaround.

Docs only.

gburd added 3 commits October 30, 2026 00:19
…, how to contribute

- "Measured against Berkeley DB 5.3.28": v2026.10.8 / 5.3.28 on one
  c6id.metal, from test/bench/XREL-2026-10.md (addendum).  Faster
  concurrent reads, scans and TPC-C-like; single-threaded about the
  same; still slower on inserts and TPC-B write-no-sync at 16-32
  threads.
- "What the fork has changed since 5.3.28", grouped as concurrency,
  correctness, features, portability and release discipline.
- Contributing: how to report a bug, the security route, the PR steps,
  what a performance claim needs, and where fixes land (master first,
  backport-lts for an LTS line).
- RFCs: when a change needs one.
- Release table: v2026.10.8 as the current regular release.
@github-actions

Copy link
Copy Markdown
Contributor

Coccinelle convention checks

No new violations. ✅

Resolved since baseline (3) -- update dist/cocci/baseline.txt to lock these in.
rule_mutex_unbalanced|MUTEX_UNBALANCED|src/btree/bt_curadj.c|return (ret);
rule_mutex_unbalanced|MUTEX_UNBALANCED|src/crypto/mersenne/mt19937db.c|return (ret);
rule_mutex_unbalanced|MUTEX_UNBALANCED|src/mp/mp_register.c|return (ret);

@github-actions

Copy link
Copy Markdown
Contributor

ABI diff vs v2026.10.8 (libabigail — authoritative)

abidiff exit bitmask: 0

Removed exported symbols (nm -D, _NNNN version suffix normalized)

None.


Advisory: libabigail/nm is the authoritative binary-ABI check; Coccinelle is complementary source-level early warning. See dist/cocci/README.md.

@gburd
gburd merged commit e1fe5c2 into master Oct 30, 2026
58 checks passed
@gburd
gburd deleted the docs/readme-2026-10-8 branch October 30, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant