Repository navigation
docs: add unified LocalStack .NET roadmap - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The organization has separate product plans but no shared view of priorities or dependency adoption. Add one roadmap covering Client, Aspire Hosting, BadgeSmith and the Serverless Demo, with supporting repositories and archives explicitly scoped.
The roadmap prioritizes qualification of Native AOT/framework work and authenticated current-image tests, then propagates validated published updates through actual consumers. It separates proposals, merged source, published packages and runtime evidence, and links the maintenance playbook.
Validation: current public GitHub/NuGet/source evidence; independent source and contract reviews; complete accounting for the prior candidate inventory; Markdown links, public-content boundaries and whitespace checks. Documentation only; runtime tests, builds, Docker and cloud probes were not run.
The profile entrypoint takes effect when this PR is merged. Product repositories retain their detailed plans and support contracts.