Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Will there be newer versions of Blazor Wasm 3.2.0 packages released before November #23388

Closed
bancroftway opened this issue Jun 26, 2020 · 3 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved
Milestone

Comments

@bancroftway
Copy link

One of the questions being asked by our management, when we propose working on a Blazor project, is that since it is such a new technology, if there are critical bugs found, how and when the fixes will be available.

I assume that since Blazor is released as a set of packages, there would be new versions of these packages released...but I wanted to double-check if this assumption is correct. Any guesstimates when the next revision of 3.2.0 Blazor packages will be in preview, if any?

@javiercn
Copy link
Member

@bancroftway thanks for contacting us.

We will evaluate incoming issues as we do with other products and will patch the ones we determine are severe enough to require servicing and those new packages will be released in the regular .NET Core patch schedule.

/cc: @danroth27

@javiercn javiercn added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Jun 26, 2020
@danroth27
Copy link
Member

Hi @bancroftway.

Blazor WebAssembly now ships as part of the .NET Core 3.1 SDK. Any critical fixes for Blazor WebAssembly would be handled as part of our monthly .NET Core 3.1 patches. For example, we have couple of fixes coming with the July patch release. These patch updates are generally small and highly compatible.

The next major release of Blazor WebAssembly is happening with .NET 5. We just added Blazor WebAssembly to .NET 5 for Preview 6. .NET 5 is schedule to ship in Nov of this year. You can see the Blazor related features we are working on for .NET 5 in our roadmap issue.

Please note that although Blazor WebAssembly 3.2 ships with the latest .NET Core 3.1 SDK, it does not inherit the LTS status of .NET Core 3.1. This was the first release of Blazor WebAssembly, and we prefer to ship something more than once before giving it LTS status. Blazor WebAssembly 3.2 is a Current release, which means that once we ship .NET 5 later this year you'll need to update within three months to stay in support. We expect .NET 5 to be a highly compatible release.

@danroth27 danroth27 added the ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. label Jun 26, 2020
@ghost ghost added the Status: Resolved label Jun 26, 2020
@danroth27 danroth27 added this to the Discussions milestone Jun 26, 2020
@bancroftway
Copy link
Author

Thank you so much for providing clarification.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants