-
Notifications
You must be signed in to change notification settings - Fork 333
Can we get a new (and possibly non-beta-) release? #470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Looking forward to a reply or feedback from the maintainers on this question. |
It's been a year since there's been a release? cc: @bagajjal @manojampalam any insights? |
Is this project still maintained ? |
Good question, wish I knew the exact answer. Although there could be a fairly useful comment in #466 (comment):
See also:
So maybe it would be better to repost the question in https://github.com/PowerShell/Win32-OpenSSH/issues |
Seems that it is indeed still maintained, see here. The documentation is very haphazard, which is a real shame because it's a great project. (It makes a world of difference for remote-administering Windows machines when you don't want to go down the Active Directory rabbit hole...) |
All GitHub releases are marked as beta as we don't have a servicing channel to provide the security fixes. |
Good to know.
Then just do that as everyone else that releases on GH: Make a 8.5.0 release and if you see anything needs to be fixed or security fixes are to taken over release a 8.5.1 and so on. |
All releases on this repo are labeled as beta as there is not a proper servicing/support channel, this will likely not change. The versions that are included in-box on Windows are the only supported versions. If we did move the 8.x.0 -> 8.x.1 scheme, there is no denotation that states the release is unsupported, thus the beta tag in the release name. |
Thanks that makes that clear, I someday have to check the wiki and README if those informations are found there and otherwise open a new issue about the "beta-documentation" (of course I'd like to have Windows OpenSSH supported also on older versions of Windows Server, but I guess that's unlikely to happen). One thing that comes back with the changes and the upcoming release in this month: What is the intended sharing process with upstream? #471 possible would benefit of an update, too... |
Github OpenSSH releases are supported from windows 7 and up. |
Yes, but those are only beta releases and the non-beta are currently not uploaded there, which means: Win7, Win2012R2 Server and others only get the "beta" versions. If you could upload the non-beta executables as a GH release (possibly before using the common update channels to serve those to the "common user") then users can subscribe to that, know that a new version is there and update their older systems or know they'll get those soon via common update. |
@GitMensch - We don't have any plans to release non-beta Github releases. C:> az vm extension set --publisher "Microsoft.Azure.OpenSSH" -n WindowsOpenSSH --resource-group myrg --vm-name myvm C:> az vm open-port --resource-group myrg --name myvm --port 22 |
We track issues in a different repo https://github.com/PowerShell/Win32-OpenSSH/issues. |
The changes since the last "beta" v8.1.0.0...latestw_all seem relevant enough to publish a new version and as OpenSSH (likely based on work done here) is now provided for newer Windows versions from the windows features it seems that "beta" can be dropped.
The text was updated successfully, but these errors were encountered: