Jamshed Damkewala
Jamshed Damkewala
I agree with the need to add this clarification but don't think we should pollute the official lifecycle page with the details of this exception which will no longer be...
> I think standardizing on title case or all lowercase would be a question for @jamshedd and @richlander. Let me know the preference and I'll adjust accordingly on all PRs....
> > I think we need to keep this Long Term Support (LTS) and Standard Support with that capitalization in our content/website/etc. the one exception to this is the releases.json...
The work is not funded at this point, this will likely move to 7.0.
Playing the data controller or data processor role with PII such as email addresses involves more policy and process overhead than one might imagine. I would not favor that approach,...
@richlander is the right person to answer why we took a dependency on the VS copy of the file rather than the NuGet one (or at least should be able...
agree. @leecow @rbhanda is there a reason we cannot do this for our servicing releases that do carry CVE fixes?
.NET and Visual Studio are independent products, and as you noted above each of these has its own independent support lifecycle. While this was not the news you hoped for,...
At this time there is no published schedule for Visual Studio vNext, what's released out there is VS 2022 so my expectation is .NET 8 development will be supported on...