Clarify which version of PowerShell Core supports which platform.#2677
Clarify which version of PowerShell Core supports which platform.#2677DCtheGeek merged 4 commits intoMicrosoftDocs:stagingfrom TravisEz13:Add_support_matrix
Conversation
Also, add details about EOL policy and when platforms where EOL'ed
✅ Validation status: passed
For more details, please refer to the build report. Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report. |
|
@TravisEz13 You targeted the 'staging' branch with this, but since it has a table for 6.1 support, did you want to target the 6.1 release branch instead? |
|
@DCtheGeek where are the rules for what branch to target. This is actually more about accurately showing what we support for 6.0 as the previous document had added platforms which are only supported in 6.1. |
|
@TravisEz13 I've reviewed and it can go in either, I just wanted to check. Putting in staging means it'll go to live at next big publish (once or twice a week). Putting it into release-61 means it isn't ready to be the official article yet, but when 6.1 is GA, then we'll merge that branch into live, thus publishing anything that's just waiting on 6.1. Just let me know which you'd like and I'll approve. |
| but they are not officially suppported: | ||
| but they are not officially supported: | ||
|
|
||
| * Arch Linux |
There was a problem hiding this comment.
Would it be easier to read if you put these in the table and have it say Community?
Should we include Experimental for Raspbian on 6.0 and Supported for 6.1?
We'll have to update this table again once Alpine docker image is out or just do it now.
There was a problem hiding this comment.
Raspbian isn't supported by DotNet, so I say community: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#linux
I think we should update Alpine when the work is done.
I'll update the table as suggested.
|
@DCtheGeek I don't think there is a reason to hold this for the 6.0 release. I think it's easier just to release the full thing to explain why Fedora 28 was changed. |
|
@TravisEz13 Works for me. Once Steve & Joey approve and the build passes, I'll push it forward. Thanks! |
Center align some columns
✅ Validation status: passed
For more details, please refer to the build report. Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report. |
✅ Validation status: passed
For more details, please refer to the build report. Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report. |
joeyaiello
left a comment
joeyaiello
left a comment
There was a problem hiding this comment.
Just the one language tweak, otherwise looks great. Thanks!
| but they are not officially supported. | ||
| These packages are marked as `Community` in the table. | ||
|
|
||
| Platforms listed as `Experimental` are not officially supported, but is available for experimentation of feedback. |
There was a problem hiding this comment.
"...but are available for experimentation and feedback."
✅ Validation status: passed
For more details, please refer to the build report. Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report. |
5 participants
Clarify which version of PowerShell Core supports which platform.
Also, add details about EOL policy and when platforms where EOL'ed
The language about EOL was taken from here: https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md
Version(s) of document impacted
Reason(s) for not updating all version of documents