2 ms·
> And no, the pre-release line doesn't really apply here. When you release RC2 with a Golive license and publicly state "you can be confident to use it in Produ
by Sacho 10y ago
> And no, the pre-release line doesn't really apply here. When you release RC2 with a Golive license and publicly state "you can be confident to use it in Production and we will support you" only to backtrack on it (days, weeks?) later then that's on Microsoft.
Where did they do that? Does .NET Core even have an RC2 or an RC1? Are you talking about ASP.NET Core? Where did they backtrack on the Golive license on ASP.NET Core RC2?
I don't think Microsoft has ever announced a release date for .NET Core, so why you were confident it would release at a particular point is confusing to me.
There's also never been a release date for ASP.NET Core. Certainly, RC2 took a lot longer than you would reasonably extrapolate from the speed between betas and RC1, but I don't see much support for the rest of your post in any announcements I've ever read.
- Aaronontheweb 10y agoYou're right - I got that confused with RC1. And yes .NET Core does: https://www.infoq.com/news/2016/05/dotNETcore-RC2 https://www.infoq.com/news/2016/05/dotNETcore-RC2
- Aaronontheweb 10y ago> I don't think Microsoft has ever announced a release date for .NET Core, so why you were confident it would release at a particular point is confusing to me. The expectations that were casually set by members of the team at talks, on Twitter, on Podcasts, and so forth all indicated that .NET Core's arrival was imminent. The bulk of my criticism has been that their communication strategy on its readiness has not been carefully managed. Therein lies the problem.