MegaBites-AI/Windows-powershell

1name: Release Process2description: Maintainers Only - Release Process3title: "Release Process for v7.x.x"4labels: [Issue-Meta, Needs-Triage]5body:6- type: markdown7  attributes:8    value: >9      This template is for maintainers to create an issues to track the release process.10      Please **only** use this template if you are a maintainer.11- type: textarea12  attributes:13    label: Checklist14    value: |15      - [ ] Verify that [`PowerShell-Native`](https://github.com/PowerShell/PowerShell-Native) has been updated / released as needed.16      - [ ] Check for `PowerShellGet` and `PackageManagement` release plans.17      - [ ] Start process to sync Azure DevOps artifacts feed such as modules and NuGet packages.18      - [ ] Create a private branch named `release/v6.x.x` in Azure DevOps repository.19        All release related changes should happen in this branch.20      - [ ] Prepare packages21          - [ ] Kick off coordinated build.22      - [ ] Kick off Release pipeline.23          - *These tasks are orchestrated by the release pipeline, but here as status to the community.*24          - [ ] Prepare packages25              - [ ] Sign the RPM package.26              - [ ] Install and verify the packages.27              - [ ] Trigger the docker staging builds (signing must be done).28          - [ ] Create the release tag and push the tag to `PowerShell/PowerShell` repository.29          - [ ] Run tests on all supported Linux distributions and publish results.30          - [ ] Update documentation, and scripts.31              - [ ] Update [CHANGELOG.md](../../CHANGELOG.md) with the finalized change log draft.32              - [ ] Stage a PR to master to update other documents and33                    scripts to use the new package names, links, and `metadata.json`.34          - [ ] For preview releases,35            merge the release branch to GitHub `master` with a merge commit.36          - [ ] For non-preview releases,37            make sure all changes are either already in master or have a PR open.38          - [ ] Delete the release branch.39          - [ ] Trigger the Docker image release.40          - [ ] Retain builds.41          - [ ] Update https://github.com/dotnet/dotnet-docker/tree/master/3.0/sdk with new version and SHA hashes for global tool. NOTE: this link is broken!42