Skip to content
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

Need a clear doc page that shows which OS versions Terminal will run on #15864

Closed
kilasuit opened this issue Aug 22, 2023 · 5 comments
Closed
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@kilasuit
Copy link

Coming from this issue in the PowerShell Repo (that I created) I found PowerShell has this nice easy to understand document section for supported versions of windows

This Doc is the closest similar one & I think could be updated to show where you expect Terminal to actually run, like as show above would provide much needed clarity going forward.

@kilasuit kilasuit added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Aug 22, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 22, 2023
@zadjii-msft
Copy link
Member

I mean, it's pretty front and center at the top of the README

Windows Terminal requires Windows 10 2004 (build 19041) or later

But we can just add a note at the top of that docs page too. No need to have a whole matrix of options - it's just >10.0.19041 for all terminal versions.

@kilasuit
Copy link
Author

Sorry but this is what I mean by it's not clear & why just using build numbers makes it unclear & would with a matrix with clearer notes as to why it's unsupportable on those os'es would likely have stopped you having ever had the support 2016/2019 issues being raised.
It also does not help that Windows 11 still shows up as Windows 10 in many places
being crystal clear helps stop confusion, and your docs in this case aren't crystal clear, hence the ask for a matrix.
I know to you & others within & outside Microsoft that build numbers make a lot of sense, but the way they are right now is super confusing to many of us, especially if we are managing mixed estates.

Just trying to give some honest and useful feedback here that would definitely help many going forward for what isn't really a big ask in much needed clarity.

@kilasuit
Copy link
Author

kilasuit commented Aug 22, 2023

Also I'm lucky in that I do understand build numbers to an extent having been a Windows Insider since 2014, but having to play the calculation game on things like which of the LTSC builds this is supported on, is time me & others shouldn't be needing to waste in trying to work out when a matrix would solve it

@zadjii-msft
Copy link
Member

Moved to our docs repo: MicrosoftDocs/terminal#701

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2023
@kilasuit
Copy link
Author

sorry for raising in the wrong repo @zadjii-msft & thank you for raising in the right one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants