GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — PowerShell Version Number in LICENSE.txt · Issue #9801 · PowerShell/PowerShell

PowerShell Version Number in LICENSE.txt #9801

New issue
Copy link
New issue
Copy link
Closed
Closed
PowerShell Version Number in LICENSE.txt#9801
Copy link
Labels
Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build

Description

@thecliguy
thecliguy
opened on Jun 2, 2019
Issue body actions

Steps to reproduce

The PowerShell installation MSI provides a link to the project's MIT licence (see #8846).

I have tested the MSI for 6.2.1 and 7.0.0 preview 1 on Windows 10 (1809) x64, both of which link here.

Expected behavior

The PowerShell version number in the licence should better reflect the version of PowerShell that the user is installing.

Actual behavior

The version in the licence is 6.0 irrespective of the version being installed by the user, see the first line of the licence file:

PowerShell/LICENSE.txt

Line 1 in 83708a4

PowerShell 6.0

Possible solutions

  • Change the version number in the licence file to something like PowerShell 6.0 + in order to accommodate 6.0 and later releases.
  • Remove the version number from the licence file.
  • Show only the major part of the version number, EG: PowerShell 6 and 7
  • Change the way in which the licence is displayed to reflect the specific version being installed by the user.

Activity

  1. thecliguy
    added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Jun 2, 2019
  2. Ilya (iSazonov)
    added
    WG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
    Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the product
    and removed
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Jun 3, 2019

  3. thecliguy commented on Oct 13, 2020

    @thecliguy
    thecliguy
    on Oct 13, 2020
    Author
    More actions

    Resolved by SteveL-MSFT in #12019.

  4. thecliguy
    closed this as completedon Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.