-
Notifications
You must be signed in to change notification settings - Fork 0
Milestones
List view
Planned 1.2.0 feature milestone for remaining open post-1.1.0 work. Scope: - Explore CDCavell.AsiBackbone.Aspire integration for local orchestration. - Create CDCavell.AsiBackbone.Templates dotnet new package. - Add local-development ProblemDetails diagnostics for endpoint governance failures. - Add fluent AddAsiBackbone builder facade for one-liner bootstrapping. - Add CDCavell.AsiBackbone.Testing package and test harness ergonomics. Release intent: 1.2.0 is a minor release target for new package ergonomics, host-development support, local diagnostics, testing support, and developer-experience improvements after the 1.1.x stabilization line.
No due date•15/15 issues closedPost-1.1.0 stabilization milestone for the planned 1.1.1 release. Scope: - Add focused xUnit tests to improve Core line and branch coverage. - Close branch gaps in capability grant validation, signing verification, canonical payload building, governance emission/outbox behavior, and DLP/classification policy. - Refresh quality/coverage documentation where needed. - Keep changes limited to testing, documentation cleanup, and non-breaking maintenance unless a defect is discovered during test expansion. Release intent: 1.1.1 should remain a compatible patch release focused on validation hardening and documentation cleanup after 1.1.0.
No due date•28/28 issues closedThis milestone extends AsiBackbone beyond the 1.0.0 neutral governance spine by adding observability, durable outbox patterns, lifecycle event modeling, and optional governance-emission providers. The goal is to make AsiBackbone decisions, acknowledgments, capability grants, and audit receipts easier to persist, trace, export, and enrich without coupling Core to any specific cloud vendor or compliance platform. Core work in this milestone should remain vendor-neutral: emission abstractions, lifecycle event stages, telemetry and trace fields, durable outbox contracts, signing-ready receipt/key abstractions, and clear production wording around audit, tamper-evidence, and current limitations. Provider-specific work should live in optional packages that depend on Core, never the reverse. Azure Monitor, Event Hubs, Microsoft Purview, OpenTelemetry, and DLP-related integrations should be implemented as separable providers so consumers can adopt only the integrations they need. Success for this milestone means AsiBackbone can emit governance-relevant events through stable neutral seams, persist them durably when needed, and support enterprise observability and governance enrichment while preserving the project’s primary identity as a host-owned, vendor-neutral governance spine.
No due date•34/34 issues closedPrepare the ASIBackbone package family for stable release. This milestone should focus on API review, documentation completeness, package metadata, CI validation, compatibility checks, and release readiness for the initial stable public package set.
No due date•16/16 issues closedAdd sample usage and host validation scenarios, including a NetCoreApplicationTemplate-based sample host and a plain ASP.NET Core host where useful. Samples should demonstrate that ASIBackbone remains independent while integrating cleanly into host-owned infrastructure.
No due date•2/2 issues closedAdd optional ASP.NET Core integration for service registration, endpoint or middleware hooks, current-user/current-actor seams, and host application integration. This milestone should support use with or without NetCoreApplicationTemplate.
No due date•8/8 issues closedAdd optional EF Core integration for host-owned DbContext usage. This milestone should provide ModelBuilder extension methods, entity type configurations, persistence defaults for ASIBackbone entities, and integration tests while keeping the host application responsible for DbContext ownership and migrations.
No due date•10/10 issues closedEstablish the initial CDCavell.ASIBackbone.Core package with dependency-light domain abstractions, base entity contracts, result primitives, package metadata, tests, and baseline documentation. This milestone should avoid EF Core, ASP.NET Core, and NetCoreApplicationTemplate dependencies.
No due date•14/14 issues closed