Create release process issue template (#8417)

* create release process issue template
* Add a security issue template as well
This commit is contained in:
Travis Plunk
2018-12-12 12:24:12 -08:00
committed by GitHub
parent 5478cf6f66
commit c76a3d7bb4
2 changed files with 54 additions and 0 deletions
+37
View File
@@ -0,0 +1,37 @@
---
name: Release Process
about: Maintainers Only - Release Process
---
<!--
This template is for maintainers to create an issues to track the release process.
Please **only** use this template if you are a maintainer.
-->
# Release Process for v6.x.x
- [ ] Create a private branch named `release-v6.x.x` in Azure Dev Ops repository.
All release related changes should happen in this branch.
- [ ] Run tests on all supported Linux distributions and publish results
- [ ] Prepare packages
- [ ] Build release packages
- [ ] Sign the MSI packages and RPM package.
- [ ] Install and verify the packages.
- [ ] Trigger the docker staging builds (signing must be done.)
- [ ] Update documentation, and scripts.
- [ ] Update [CHANGELOG.md](../../CHANGELOG.md) with the finalized change log draft.
- [ ] Update other documents and scripts to use the new package names, links, and `metadata.json`.
- [ ] Create NuGet packages and publish them to `powershell-core` feed.
- [ ] Run release build to publish Linux packages to Microsoft YUM/APT repositories.
- [ ] Create the release tag and push the tag to `PowerShell/PowerShell` repository.
- [ ] Run release build to create the draft and publish the release in Github.
- [ ] For preview releases,
merge the release branch to Github `master` with a merge commit.
- [ ] For non-preview releases,
make sure all changes are either already in master or have
- [ ] Delete the release branch.
- [ ] Trigger the docker image release.
- [ ] Test and publish NuGet packages on NuGet.org
- [ ] Retain builds.
@@ -0,0 +1,17 @@
---
name: Security Issue
about: Security Issue
---
# Security Issue
Excerpt from [Issue Management - Security Vulnerabilities](https://github.com/PowerShell/PowerShell/blob/master/docs/maintainers/issue-management.md#security-vulnerabilities)
> If you believe that there is a security vulnerability in PowerShell Core,
it **must** be reported to [secure@microsoft.com](https://technet.microsoft.com/security/ff852094.aspx)
to allow for [Coordinated Vulnerability Disclosure](https://technet.microsoft.com/security/dn467923).
**Only** file an issue, if secure@microsoft.com has confirmed filing an issue is appropriate.
When you have permission from secure@microsoft.com to file an issue here,
please use the Bug Report template and state in the description that you are reporting the issue in coordination with secure@microsoft.com.