[release/v7.4] Fix up SSHConnectionInfo ssh PATH checks#26167
[release/v7.4] Fix up SSHConnectionInfo ssh PATH checks#26167pwshBot wants to merge 2 commits intoPowerShell:release/v7.4from
Conversation
…pace is not available (PowerShell#25780)
|
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
adityapatwardhan
added
the
CL-Engine
microsoft-github-policy-service
bot
added
the
Review - Needed
|
First, we need to backport this to 7.5, but even then, I'm not sure this meets the bar for LTS backport. |
|
I really think more needs to go into what qualifies for a backport then. Like an official document in the repo. It seems like it’s whatever arbitrary decision made by the pwsh team. Sorry if it sounds rude but this is a pretty simple fix that has been waiting to be included in an official release for 5 months now. Even then this backport was opened 3 months ago and only now a decision/review over it has been made. I wouldn’t be pushing for a backport for bugfixes if we didn’t have to wait so long for anything. |
|
@jborean93 They should update most of the documents in this project, but I believe they are forced to follow the internal requirements of MSFT, which cannot be disclosed. This is a fundamental problem in this project. The situation seems to be better in .The Net Runtime project that is under .Net Foundation. PowerShell project probably should have followed this path. |
microsoft-github-policy-service
bot
removed
the
Review - Needed
microsoft-github-policy-service
bot
added
the
Review - Needed
|
This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days. |
5 participants
Backport of #25780 to release/v7.4
Triggered by @adityapatwardhan on behalf of @jborean93
Original CL Label: CL-Engine
/cc @PowerShell/powershell-maintainers
Impact
Choose either tooling or Customer impact.
Tooling Impact
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]