Repository navigation
Roadmap #34
Description
The plan, one level up. Each sub-issue is an epic: a release (with a milestone of the same name) or a theme that spans releases.
How issues and PRs are labelled (the same scheme as EntglDb/BLite):
- Type: exactly one of
bug,enhancement,documentation,tests,chore. package/*: the shipped packages affected:package/core,package/nodatime,package/efcore,package/efcore-nodatime.area/*: the concern across packages:ranges,range-set,value-sets,json,literals,aot,release.severity/*: bugs only.critical,high,mediumorlow.silent: a bug that answers wrongly without throwing. Up to 10.0.0 its fix went in the next major. After 10.0.0 it ships as a minor on every supported line, never a patch, and that minor's changelog entry opens with### Changed answers, a row linking the issue and itsdocs/migration.mdsection (CONTRIBUTING.md, "A fix that changes an answer"; PR hygiene checks the row).breaking: anything that changes an existing answer or signature.found-by/oracle: found by the generated-oracle machinery.stacked(PRs): the base is another open PR. Merge them in order.- Releases: each release is an
epicwith a milestone. Its work is attached as sub-issues and carries the same milestone. A PR carries its issue's labels and saysCloses #n.
Activity
CaffeinatedCoder commentedon Oct 18, 2026
Decisions recorded 2026-10-18 (research session on the v10 questions):
11.0.0-preview.N(epic Epic: 11.0.0 #147). The 14 silent fixes (Epic: 10.0.0 #58) land onmainfirst and merge forward. Issue CONTRIBUTING promises a parallel 9.x line after 10.0.0; SECURITY.md supports one #86's "one supported version" is reversed by Two supported lines: policy, branch rules, SECURITY rows, and the silent-fix rule as a minor with a changed-answers section #151, which also rewrites the silent-fix rule for two lines. EFCore.ComplexIndexes adopts the same scheme, labels and lines the same day (its roadmap and epics).DoubleRange/DoubleSetover a customfloat8range, a 10.x minor (backlog). The custom-type tier (timerange,float8range) is documented as a table, not as a new category.LTreeis translation-only and its maintainers declined client-side semantics (efcore.pg #2330, #3610, #3876); the gap is real, but label paths are a different algebra. It goes to the sibling hierarchies package, reusing this repo's parity-oracle tooling, when a consumer exists.closed/unionrewrite of the five variants (Compile probe: C# 15 closed hierarchies and union types for the five variants, on net10.0 and net11.0 #148, Mark the range unions closed (C# 15) for compile-time exhaustiveness, on both lines #149) is the 11.0.0 headline.