Milestones
List view
Error severity, verify contract, resolved config, docs and release gating.
No due date•0/5 issues closedlsm-spec conformance, bidirectional Midge qualification, fuzz/bench/soak and CI lanes.
No due date•0/13 issues closedLocal/cloud lease expiry, parsing, epoch floors and takeover behavior vs Midge 0.1.1 and lsm-spec lease.md.
No due date•0/12 issues closedCloud WAL catalog, DDL, recovery, hybrid local-budget, provider and credential gaps vs Midge 0.1.1.
No due date•0/31 issues closedRead-path, compaction, flush, WAL and spill work that is unbounded or unfair relative to Midge 0.1.1.
No due date•0/24 issues closedGaps that can lose acknowledged data, brick a database, or give wrong answers. Baseline: Midge 0.1.1 (7d39f86) vs Pants 2507c66.
No due date•6/21 issues closedClose the evidence-backed deltas against current Midge main and make Pants releasable for large disk-resident workloads. Includes #219, bounded runtime-response semantics, cloud preflight/OCI/lease configuration, current bidirectional compatibility, persisted-decoder fuzzing, operator documentation, and NuGet release qualification. Excludes the intentionally deferred .NET 11 upgrade.
No due date•6/9 issues closedDeferred framework-dependent dependency work. Entry gate: .NET 11 GA plus a separate approved target-framework decision. Exit: native Zstd interoperability is proven and the LZ4 dependency decision is explicitly documented. Do not schedule before the entry gate.
No due date•0/1 issues closedHarden provider HTTP behavior, cloud GC/DDL, hybrid eviction, and lease fencing under races and indeterminate outcomes. Exit: mutations are correctly classified and fenced; GC is anomaly-tolerant; hybrid storage stays bounded without evicting unmirrored data; provider-shaped tests pass. Depends on M7-M8 durability contracts.
No due date•35/35 issues closedMake cache concurrency/eviction and leveled-compaction planning/output safe under sustained production-shaped load. Exit: no use-after-dispose or eviction deadlock; output partitions preserve key/range invariants; planner failure cannot starve unrelated work. Depends on M7; coordinate recovery cases with M8.
No due date•17/17 issues closedEnsure flush, recovery, and local I/O preserve acknowledged data and self-heal predictably across crashes and partial failures. Exit: no salvage-induced loss of valid SSTs; publication/retry/backpressure failure modes are classified; reopen tests pass in Strict and Salvage. Depends on M7 format semantics.
No due date•19/19 issues closedMake WAL, SST, and manifest parsing/writing spec-conformant and corruption-safe. Exit: confirmed format defects are fixed first; every normative decoder invariant has focused adversarial coverage; Midge fixtures and persisted discriminants remain compatible. Prerequisite for M8 and release qualification.
No due date•37/37 issues closedRemove the measured snapshot, transaction, commit, lifecycle, and cloud structural bottlenecks before considering leaf-level allocation tuning. Work is TDD-first and preserves Midge behavior and persisted-format compatibility.
No due date•9/9 issues closed