PowerShell / PowerShell/Win32-OpenSSH
We need production releases not just beta releases
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's current GitHub release process and how beta releases become Windows packages. Done would require an agreed, documented production-release process and evidence that it can be used for a stable release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- operating-systems, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100