Roadmap #35

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. The long-form design notes stay in ROADMAP.md; the work is tracked here.

How issues and PRs are labelled (the same scheme as CodoMetis.ValueRanges and EntglDb/BLite):

• Type: exactly one of bug, enhancement, documentation, tests, chore.
• package/*: the shipped packages affected: package/core, package/postgresql, package/sqlserver.
• area/*: the concern across packages: indexes, expression-indexes, constraints, migrations, release.
• severity/*: bugs only. critical, high, medium or low.
• silent: a bug that answers wrongly without throwing (a migration that creates a different index or constraint than the model declared is the typical case here).
• breaking: anything that changes an existing answer or signature.
• stacked (PRs): the base is another open PR. Merge them in order.
• Releases: each release is an epic with a milestone. Its work is attached as sub-issues and carries the same milestone. A PR carries its issue's labels and says Closes #n.
• Lines: from November 2026 there are two supported lines, one per EF Core major (issue Support for previous EF Core versions ? #3). EFCore.ComplexIndexes 5.x is on EF Core 10 / .NET 10 (LTS, to 2028-11, branch release/5.x, fixes only after 5.5.0, Epic: 5.5.0 — EFCore.ComplexIndexes stays the EF Core 10 package #36). Its successor CodoMetis.EFCore.SchemaKit 11.x is on EF Core 11 / .NET 11 (branch main, Epic: CodoMetis.EFCore.SchemaKit 11.0.0 — the EF Core 11 successor #37). A fix for both goes to main first and is cherry-picked with -x.