Microsoft.OpenSSH.Preview - Is it really?

[garrgar]

Microsoft's OpenSSH releases are done via PowerShell/Win32-OpenSSH (although developed in a different repository). They used to be labeled as betas, but are now called previews. However, it's been explained there that the only reason they are not marked as releases is because they are not supported in GitHub, and of course, Microsoft supports those shipped via Windows updates. It was further said that the Windows releases were the same quality as the corresponding GitHib releases. They just have a different cadence.

So, these releases will never be labelled as non-preview/non-beta. Can we start using the identifier Microsoft.OpenSSH for these gh releases?

Here's one of the quotes I'm basing this on:

"There is no "non-beta" release that is available on GitHub. This is only due to the level of support we are able to offer on the GitHub releases. All "GA" releases are made through Windows and Windows Update, these versions are officially supported via Windows Support. There are no differences in quality for a Windows vs GitHub release. All GitHub releases should be stable."

[SteveL-MSFT]

To be specific, the releases on the Microsoft OpenSSH GitHub repo are labeled preview because they are not supported by Microsoft support. They are supported via our GitHub repo. This means using a preview release you don't get Enterprise Assurance support, for example. The resulting release that shows in inbox in Windows is one of the versions we ship as preview, but only after it's gone through bake time and testing. The GitHub releases are intended to get early feedback to help us decide when it's ready to be inbox in Windows and supported for Production. I think this issue is probably better to discuss with the team in the OpenSSH repo and not this one.