X Tutup
The Wayback Machine - https://web.archive.org/web/20221021161306/https://github.com/PowerShell/PowerShell/pull/18304
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

Jump to bottom

Replace win7 runtime with win8 and remove APISets #18304

Merged
merged 6 commits into from Oct 18, 2022
Merged

Replace win7 runtime with win8 and remove APISets #18304

merged 6 commits into from Oct 18, 2022

Conversation

adityapatwardhan
Copy link
Member

@adityapatwardhan adityapatwardhan commented Oct 14, 2022 •
edited by TravisEz13

PR Summary

Replace the runtime for builds from win7 to win8 as we are not going to support windows 7 anymore.
Remove APISets which are deprecated.

PR Context

PR Checklist

@ALIENQuake
Copy link

ALIENQuake commented Oct 15, 2022

@adityapatwardhan Hi,

Does after merging this PR, Windows 7 won't have any PS 7 LTS version?

@xtqqczze
Copy link
Contributor

xtqqczze commented Oct 17, 2022 •
edited

@ALIENQuake
PowerShell OS support is linked to .NET support policy. See dotnet/core#7556 for discussion of .NET support for Windows 7.

@iSazonov
Copy link
Collaborator

iSazonov commented Oct 17, 2022

dotnet/core#7556 says about EOL on Windows 8.1 too.

@xtqqczze
Copy link
Contributor

xtqqczze commented Oct 17, 2022

dotnet/core#7556 says about EOL on Windows 8.1 too.

I expect we will maintain support for win81-x86 and win81-x64 target platforms due to Windows Server 2012/R2 ESU.

https://learn.microsoft.com/en-us/dotnet/core/rid-catalog#windows-rids
https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates

@daxian-dbw
Copy link
Member

daxian-dbw commented Oct 17, 2022

@adityapatwardhan Win8.1 support will end on January 10, 2023, same time as the Win7, so shall we directly use win10 as the RID?

@xtqqczze
Copy link
Contributor

xtqqczze commented Oct 17, 2022

@adityapatwardhan Win8.1 support will end on January 10, 2023, same time as the Win7, so shall we directly use win10 as the RID?

But Windows Server 2012 R2 uses the same RIDs and is supported through ESU until October 13, 2026.

@pull-request-quantifier
Copy link

pull-request-quantifier bot commented Oct 17, 2022

This PR has 598 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details 

Label      : Extra Large
Size       : +52 -546
Percentile : 86.6%

Total files changed: 22

Change summary by file extension:
.yml : +9 -9
.wxs : +0 -492
.psm1 : +18 -18
.csproj : +6 -8
.ps1 : +19 -19

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍  👌  👎 (Email)
Customize PullRequestQuantifier for this repository.

@iSazonov
Copy link
Collaborator

iSazonov commented Oct 18, 2022

@adityapatwardhan Win8.1 support will end on January 10, 2023, same time as the Win7, so shall we directly use win10 as the RID?

But Windows Server 2012 R2 uses the same RIDs and is supported through ESU until October 13, 2026.

So right question is about ESU supporting pwsh 6 on the Win2012/8 :-)

Although it looks very funny - MSFT spent a year making .Net 7 on Windows 7 and just before the release decided that .Net 7 would not work/supported on Windows 7.

@adityapatwardhan adityapatwardhan marked this pull request as ready for review Oct 18, 2022
@TravisEz13 TravisEz13 added the Breaking-Change breaking change that may affect users label Oct 18, 2022
@adityapatwardhan adityapatwardhan merged commit cc86f9f into PowerShell:master Oct 18, 2022
45 checks passed
@adityapatwardhan adityapatwardhan deleted the RemoveAPISEt branch Oct 18, 2022
@adityapatwardhan adityapatwardhan mentioned this pull request Oct 18, 2022
Open
2 tasks
@daxian-dbw daxian-dbw assigned TravisEz13 and unassigned daxian-dbw Oct 18, 2022
adityapatwardhan added a commit to adityapatwardhan/PowerShell that referenced this pull request Oct 18, 2022
@adityapatwardhan
Revert "Replace win7 runtime with win8 and remove APISets (PowerShell…
1d1e4f1 
…#18304)"

This reverts commit cc86f9f.
adityapatwardhan added a commit that referenced this pull request Oct 18, 2022
@adityapatwardhan
Revert "Replace win7 runtime with win8 and remove APISets (#18304)" (#…
813d388 
…18322)
@xtqqczze
Copy link
Contributor

xtqqczze commented Oct 19, 2022

So right question is about ESU supporting pwsh 6 on the Win2012/8 :-)

We don't support PowerShell Core 6 on any platform.

As per documentation, long-term-support for PowerShell is based on the .NET support lifecycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TravisEz13 TravisEz13

@daxian-dbw daxian-dbw

@anmenaga anmenaga

@PaulHigin PaulHigin

Assignees

@TravisEz13 TravisEz13

Labels
Backport-7.3.x-Consider Breaking-Change breaking change that may affect users Extra Large
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
6 participants
@adityapatwardhan @ALIENQuake @xtqqczze @iSazonov @daxian-dbw @TravisEz13
X Tutup