You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wade, Tom ... I'm only able to describe the new process for the Blazor features. I'm not aware of how main doc set features will be worked, but I assume the PU aspects will be the same/similar.
For Blazor node content, we'll use the following approach ...
PU engineers will ...
Open issues (from the bottom of articles if they know where the content will go), assign 🦖 (and possibly themselves), and provide draft feature coverage no later than two weeks prior to release, which is MAY 27. 🦖 will not proactively provide draft feature content going forward.
Add a comment to this issue with a feature title and cross-link to the issue that they opened.
Description
cc: @danroth27 @wadepickett @tdykstra
Wade, Tom ... I'm only able to describe the new process for the Blazor features. I'm not aware of how main doc set features will be worked, but I assume the PU aspects will be the same/similar.
For Blazor node content, we'll use the following approach ...
Links ...
dotnet/aspnetcore
P5 milestone filtered issuesPage URL
https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-10.0?view=aspnetcore-9.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-10.0.md
Document ID
a7ad4b01-2333-32d8-b759-e044edfb9102
Platform Id
2f8fb8ab-5309-0a77-987a-c867c6517d2b
Article author
Various
Metadata
Related Issues
The text was updated successfully, but these errors were encountered: