Skip to content

PowerShell 6.0.1-GA Release #5887

Closed
Closed

Description

From: https://github.com/PowerShell/PowerShell/blob/master/docs/maintainers/releasing.md

  • Create a branch named 6.0.1 in PowerShell/PowerShell repository.
    All release related changes should happen in this branch.
  • Run tests on all supported Linux distros and publish results
  • Prepare packages
    • Build release packages
    • Sign the MSI packages and RPM package.
    • Install and verify the packages.
  • Update documentation, scripts and Dockerfiles
    • Update CHANGELOG.md with the finalized change log draft.
    • Update other documents and scripts to use the new package names and links.
  • Verify the release Dockerfiles.
  • Create NuGet packages and publish them to powershell-core feed.
  • Publish Linux packages to Microsoft YUM/APT repositories.
  • Create the release tag and push the tag to PowerShell/PowerShell repository.
  • Create the draft and publish the release in Github.
  • Merge the release branch to master and delete the release branch.
  • Trigger the release docker builds for Linux and Windows container images.
    • Linux: push a branch named docker to powershell/powershell repository to trigger the build at powershell docker hub.
      Delete the docker branch once the builds succeed.
    • Windows: queue a new build in PowerShell Windows Docker Build on VSTS.
  • Verify the generated docker container images.

Activity

  1. changed the title [-]6.0.1-GA Release[/-] [+]PowerShell 6.0.1-GA Release[/+] on Jan 12, 2018
  2. bergmeister commented on Jan 12, 2018

    @bergmeister
    Contributor

    Travis Plunk (@TravisEz13) : Shouldn't the branch be called 6.0.1 then? Can you please give details about why the patch is needed or is this due to the versioning problem with the package managers?

  3. TravisEz13 commented on Jan 12, 2018

    @TravisEz13
    MemberAuthor

    There will be no code changes other than the version. So, we are using the existing branch. Yes, we are doing this release to address the issue with the package managers.

  4. TravisEz13 commented on Jan 17, 2018

    @TravisEz13
    MemberAuthor

    Well, no product code changes. One test had to be updated.

  5. TravisEz13 commented on Jan 17, 2018

    @TravisEz13
    MemberAuthor

    We are considering taking PR #5903 as well.

  6. TravisEz13 commented on Jan 23, 2018

    @TravisEz13
    MemberAuthor
    OS                          Total Pass Fail
    --                          ----- ---- ----
    CentOS Linux 7 (Core)        7629 6043   17
    Debian GNU/Linux 8 (jessie)  7629 6060    1
    Debian GNU/Linux 9 (stre...  7629 6060    1
    openSUSE Leap 42.3           7629 6060    2
    Red Hat Enterprise Linux     7629 6042   19
    Ubuntu 14.04.5 LTS           7629 6060    1
    Ubuntu 16.04.3 LTS           7629 6060    1
    Ubuntu 17.04                 7629 6060    1
    
  7. TravisEz13 commented on Jan 26, 2018

    @TravisEz13
    MemberAuthor

    Linux repos are being a bit slow. Docker files are waiting for the Linux repos to have the package available.

  8. TravisEz13 commented on Jan 26, 2018

    @TravisEz13
    MemberAuthor
  9. TravisEz13 commented on Jan 26, 2018

    @TravisEz13
    MemberAuthor

    cask update merged

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions