You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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.
Activity
[-]6.0.1-GA Release[/-][+]PowerShell 6.0.1-GA Release[/+]bergmeister commentedon Jan 12, 2018
Travis Plunk (@TravisEz13) : Shouldn't the branch be called
6.0.1then? Can you please give details about why the patch is needed or is this due to the versioning problem with the package managers?TravisEz13 commentedon Jan 12, 2018
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.TravisEz13 commentedon Jan 17, 2018
Well, no product code changes. One test had to be updated.TravisEz13 commentedon Jan 17, 2018
We are considering taking PR #5903 as well.
TravisEz13 commentedon Jan 23, 2018
TravisEz13 commentedon Jan 26, 2018
Linux repos are being a bit slow. Docker files are waiting for the Linux repos to have the package available.
TravisEz13 commentedon Jan 26, 2018
cask update PR Homebrew/homebrew-cask#43182
TravisEz13 commentedon Jan 26, 2018
cask update merged