Required for PowerShell/PowerShellEditorServices#2225.

The bullet style was changed in order to satisfy the Markdown linter 🙃

Also required for PowerShell/PSScriptAnalyzer#2070.

This removes the -Daily flag from the install-powershell.ps1 script as daily builds have not been posted in a year, and Aditya Patwardhan (@adityapatwardhan) says there are no current plans to resume doing so.

We have a request to have daily build #24566

In my understanding, daily builds are the only way for partner teams to continuously test their products.
This means that we will learn about regression only after the next preview release and only if they use it for tests.
Obviously, it's better for them to test on a daily basis than to patch up problems a year later in an emergency but we even deprived them of the opportunity.

Andy Jordan (@andyleejordan) should add a parameter alias to "Daily" to not break existing scripts. I'd say this merge as-is after that, but then a follow-on should replace daily with "CIBuild" or "GHBuild" to fetch the latest commit azdo build.

Ilya (@iSazonov) per my comments on that, a "latest main commit build" is a better approach than a daily since tests are enforced for main commits.

Ilya (@iSazonov) per my comments on that, a "latest main commit build" is a better approach than a daily since tests are enforced for main commits.

It depends on the needs of that project. If they want, they can track each pwsh PR and upload artifacts from it.
I would speculate that for most projects this is too expensive and doesn't make sense. Most likely, they run a full set of functional tests once a day or less.

Ilya (@iSazonov) per my comments on that, a "latest main commit build" is a better approach than a daily since tests are enforced for main commits.

It depends on the needs of that project. If they want, they can track each pwsh PR and upload artifacts from it. I would speculate that for most projects this is too expensive and doesn't make sense. Most likely, they run a full set of functional tests once a day or less.

Then they can still do that, and they'll get whatever the latest PR branch is available when they schedule their job to run on a daily basis. Solves both problems :)

Dailies are an outdated development concept from the days where most work happened "during the day" and commit checks were rare. Since PowerShell has extensive gatekeeping on the main branch, pretty much every main commit can probably be considered to be fairly stable and unbroken at least for the vast majority of test cases, so it makes sense to provide an easy way to consume these artifacts that are already being built.

Andy Jordan (@andyleejordan) should add a parameter alias to "Daily" to not break existing scripts. I'd say this merge as-is after that, but then a follow-on should replace daily with "CIBuild" or "GHBuild" to fetch the latest commit azdo build.

Yeah, I'm wondering if the nicer thing to do is a) warn and just install the preview instead, or b) warn and exit with error. Right now it fails and that hasn't been breaking anyone so B is an option, but A is an option, though it's kind of a lie.

Yeah, I'm wondering if the nicer thing to do is a) warn and just install the preview instead, or b) warn and exit with error. Right now it fails and that hasn't been breaking anyone so B is an option, but A is an option, though it's kind of a lie.

Travis Plunk (@TravisEz13) what would you prefer here and what do we want to communicate about the future of the daily build here?

Travis Plunk (@TravisEz13) waiting on a decision from you / maintainers ☺️

Also noting that we'll want to cleanup:

• vscode-powershell
• Homebrew

I never got an answer so I'm going with option A.

Aditya Patwardhan (@adityapatwardhan) can you review this please?

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author