search

PowerShell / Win32-OpenSSH

Win32 port of OpenSSH
7.2k stars 739 forks source link

We need production releases not just beta releases #2196

Open joshudson opened 5 months ago

joshudson commented 5 months ago

Summary of the new feature / enhancement

Ultimately, the problem with OpenSSH shipping with windows is it's way behind and not being updated.

People still hit https://github.com/PowerShell/Win32-OpenSSH/issues/1322 (largely without knowing what it is) because the Windows packages are still behind and still have this bug in it.

If they know what it is, the problem's worse. The beta releases become the production releases.

Proposed technical implementation details (optional)

Ship production releases from GitHub when ready. Looking at the current status of stuff this should be something like once a year.

maertendMSFT commented 4 months ago

I answered a similar question in this discussion (https://github.com/PowerShell/Win32-OpenSSH/discussions/2136).

Generally, the releases on GitHub are marked "beta" as we cannot meet the servicing requirements to support each release. They are provided "as is" and we maintain a best effort to fix and service them as necessary. This is not the case for the Windows released versions, which are covered by Microsoft/Windows support.

The quality of the release is not the reasoning for the "beta" tag, and the quality of the release is the same of that is shipped in Windows.

I know this is generally not the answer folks want when asking this question. Know that we are always trying to improve the avenues that Win32-OpenSSH is delivered and supported, but I do not have more information that I can share at this time.

joshudson commented 4 months ago

The problem is the Windows releases aren't being serviced. They're only getting security patches.

mgkuhn commented 4 months ago

If your actual question is “When will #1322 be fixed in Windows?”, have you contacted Microsoft Support? They will have their own bug tracking systems there, and if the question is never asked there by users, fixes might not get prioritized. (I don't know how that works specifically within MSFT, but I have seen in many other IT organizations that you often can only get the attention of management if you go through the official support channels, where they count how many people have reported a problem, otherwise it doesn't show up on their “dashboards”.)

joshudson commented 4 months ago

You have just told me, "Pay $500 to get a non-answer." My experience with Microsoft Support involving product bugs is a zero percent effectiveness rating. Even accessibility bugs don't get fixed that way.