Rich Lander

> With that change merged, we could even add the .NET 7 EOL dates back in. This PR does that. We can wait to merge this PR or unrevert the...

I'll leave that up to you. Whichever approach you prefer.

I updated all the release objects in `release-index.json`. I didn't update the old `release.json` files in absence of a reason to do so. If you have a scenario where that...

Happy to deal with the merge conflicts. However, I think I promised that I wouldn't merge these files until 7/13 (or some similar date). I'd rather wait until July patch...

Thank @mairaw!

> now changing I assume you mean "not changing" > Current - Most current release. Looks like that can still be satisfied w/o issue. I'm not sure if what it...

Ah. I see now. I'm not sure there is a big scenario for that. I think the following scenarios make sense: - Latest release - Latest LTS - this x.y...

I believe that @MattGal and @mmitche were involved in setting up those feeds. Is "Current" the same as latest? If so, we may want to undocument that and (compatibly) rename...

I just validated that `Current` work correct. ```bash rich@MacBook-Air-2 ~ % ./dotnet-install.sh -Channel Current -Verbose dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios,...

Let's just stay as-is. I will write up some docs and probably a blog post on our updated approach. I will review it with you folks to ensure everything is...