Update .NET Core versioning topic for 2.1

[jmathew]

This article suggests that the runtime and the SDK would share the same version number starting from net core 2.0:
https://docs.microsoft.com/en-us/dotnet/core/versions/

When downloading an SDK or runtime, the version number you see is going to be the same.

However if you go to the downloads page you can clearly see separate versions.

I believe this needs some clarification.

[mairaw]

Thanks for your feedback @jmathew. This has changed again and the version topic needs to be updated.

@KathleenDollard, do we have the new versioning proposal in a public repo already?

[KathleenDollard]

We have the proposal public here: dotnet/designs#29 I don't think we have an announcement yet. [https://avatars2.githubusercontent.com/u/5844318?s=400&v=4]<https://github.com/dotnet/designs/pull/29> Add plan for .NET Core SDK version numbers by ...<dotnet/designs#29> This repo is used for reviewing new .NET designs. github.com

…

________________________________ From: Maira Wenzel <notifications@github.com> Sent: Monday, February 12, 2018 1:36 PM To: dotnet/docs Cc: Kathleen Dollard; Mention Subject: Re: [dotnet/docs] Are the runtime and SDK versions supposed to be the same? (#4352) Thanks for your feedback @jmathew<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjmathew&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C4faad9b52fc544a5fa5e08d57260ad3d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540681906558594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=qmm2WhArc2WwYIrWyPN1wYlS25Js%2BJgh9vvTnz%2FTD7I%3D&reserved=0>. This has changed again and the version topic needs to be updated. @KathleenDollard<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkathleendollard&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C4faad9b52fc544a5fa5e08d57260ad3d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540681906558594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=j%2Be0cJqZGtkOSbG%2BV8ITObmxbNOupYwjv6OSMqgN%2B68%3D&reserved=0>, do we have the new versioning proposal in a public repo already? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F4352%23issuecomment-365070283&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C4faad9b52fc544a5fa5e08d57260ad3d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540681906568611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=hUpN%2F0w6vc%2F9kNitXJ6DRX%2B902kVGvvnXTwwtXFqSIk%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFktXiTMXT99AopeB68hkg0JAlseajuqks5tUK7cgaJpZM4SAEHB&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C4faad9b52fc544a5fa5e08d57260ad3d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540681906568611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=AwdT6yvsVroeAjVbREhjKjKO9qRPrukov5yaGg5BEnA%3D&reserved=0>.

[mairaw]

Thanks @KathleenDollard. I was looking for that content in the folders and not in the form of a PR.

Now, the SDK and runtime versions are not unified and are not matching the first and second positions. I'll add a quick note for now to this topic to explain this is not valid anymore for 2.1 SDK. But I'm not sure how to explain this interim version that is not unified but also doesn't reflect the long-term plan.

[KathleenDollard]

@mairaw I want to be sure I understand your comment:

2.0.x / 2.0.x easy to talk about
2.0.x / 2.1.x interim, very hard to explain
2.1.x / 2.1.xxx long term, hopefully we can explain

It would help if we had a common way to explain that interim.

The truth is we thought we could do semantic versioning for runtime and SDK independently because we release independently. That failed because of use of .NET Core 2.1 in too many places (failing to distinguish runtime and SDK). Since it failed, we developed the new version.

[mairaw]

Yes, that's exactly what I meant. That disruption in the interim is hard to explain.

[KathleenDollard]

Can you find a way to explain that we recognized that it wasn't working?

[KathleenDollard]

If we were to write a blog post explaining it, would you be able to link to it? I feel like it is easier to say "we tried something and it didn't work" in a blog post.

…

________________________________ From: Maira Wenzel <notifications@github.com> Sent: Tuesday, February 13, 2018 11:42 AM To: dotnet/docs Cc: Kathleen Dollard; Mention Subject: Re: [dotnet/docs] Are the runtime and SDK versions supposed to be the same? (#4352) Yes, that's exactly what I meant. That disruption in the interim is hard to explain. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F4352%23issuecomment-365380828&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C9e3453a209744f8fb8d908d57319f00a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636541477593183473%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=WbBc63Z%2Bb8fFr0vm48Iq4h5JnK2quLIoPR5eB%2BE2ks0%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFktXgJKZqPZ38BaioGRXU4nhT6Ufb0uks5tUeWqgaJpZM4SAEHB&data=04%7C01%7Ckathleen.dollard%40microsoft.com%7C9e3453a209744f8fb8d908d57319f00a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636541477593183473%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=TlGZKvd8W4NEV5rYkCxo0JePPwSQ7yP%2FgEogEJfP6SY%3D&reserved=0>.

[KathleenDollard]

@mairaw

Are you looking for the older proposal that said we were doing semantic versioning that explains the version numbers explained here? I can look for that if it helps. This interim version was a committed strategy, we just realized we were committed to the wrong strategy.