Perhaps worth the wait. It seems 2.2 branch inspired only by ASP.NET and EntityFramework changes.
Release 2.2.0 is expected in December and PowerShell release 6.2.0 in March. By this moment we will have a 2.2.1 service release. Also most of ordinary changes will be in 3.0 not in servicing releases and 2.2.

I don't mind if we keep the PR open for longer and accept a later preview or RTM version off .Net Core 2.2.
But I think it is good to have at least a point where we know everything is OK so that it is easier to upgrade later in case there are breaking changes in newer versions, I am happy to keep this branch up to date for the next weeks/months as a tracker for feasibility of an upgrade

I'm ok with taking .NET Core 2.2 early in our 6.2-preview releases to make sure nothing obvious gets broken and any major issues gives .NET Core time to fix in 2.2.x

Preview3 is expected in weeks aspnet/Announcements#307.

The changes look good. We are verifying with DotNet that 2.2 will be an LTS.

2.2 will not be an LTS. We should probably stay on 2.1 for now. At least until we discuss the impact of this. I like your changes to the xunit tests though. Would you mind submitting a separate PR for those? I can if you want me to.

We're having conversations with .NET Core team in terms of support alignment between PSCore6 and .NET Core. Until that gets resolved, we should only move to LTS versions of .NET Core.

This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days.
Thank you for your contributions.
Community members are welcome to grab these works.

@TravisEz13 Considering what you and @SteveL-MSFT wrote, we probably need to close this PR.

I see .Net Core 3.0 will come with tons changes, enhancement and additions. We may have to put a lot of effort into upgrading to this version. I think we can close the PR.

Ok, agreed, I will close the PR but leave the branch in case anyone in the community is interested.