Skip to content

docs: state the workload bleep is developed against, and what M11 closed - #636

Merged
oyvindberg merged 1 commit into
masterfrom
docs/status-m11
Aug 1, 2026
Merged

docs: state the workload bleep is developed against, and what M11 closed#636
oyvindberg merged 1 commit into
masterfrom
docs/status-m11

Conversation

@oyvindberg

Copy link
Copy Markdown
Owner

Two vague claims on the status page, both from the M10 era, made concrete.

"Millions of lines of source" is now measured, in a new "The workload bleep is developed against" section:

  • 12.9M lines across 57,941 files
  • bleep compiles 4.1M lines of Java and Scala, 11,896 files, 67 projects
  • 3.7M of those Java lines (92%) are generated and checked in — a SQL parser/AST family across a dozen dialects
  • ~2,300 declared tests against a corpus of 44,127 SQL files
  • a dozen or more worktrees concurrently against one shared daemon

Numbers measured with loc over a single checkout, cross-checked against git ls-files (worktrees are gitignored, so nothing is double-counted).

The bleep-bsp rewrite section still warned that edge cases were being found around concurrent workspaces, unusual project shapes and crash recovery. M11 is largely the release that went and found them, so it now names what was closed and links the release notes — while keeping the caveat that this is still milestone software.

Merging this triggers deploy-docs (path filter docs/**), which republishes bleep.build.

🤖 Generated with Claude Code

The status page carried two vague claims from the M10 era. Both are now
concrete.

"Millions of lines of source" is measured: 12.9M lines across 57,941
files, of which bleep compiles 4.1M lines of Java and Scala across
11,896 files in 67 projects. 3.7M of those Java lines (92%) are
generated and checked in. ~2,300 declared tests run against a corpus of
44,127 SQL files. Development runs across a dozen or more worktrees
concurrently against one shared daemon — the shape that produces
bleep's bugs, and the one a single-checkout workflow never sees.

And the bleep-bsp section still warned that edge cases were being found
around concurrent workspaces, unusual project shapes and crash
recovery. M11 is largely the release that went and found them, so the
section now says what was closed and links the notes, while keeping the
honest caveat that this is still milestone software.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
@oyvindberg
oyvindberg merged commit cb15f2e into master Aug 1, 2026
18 of 19 checks passed
@oyvindberg
oyvindberg deleted the docs/status-m11 branch August 1, 2026 11:38
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