Add issue verification to the release plan

Author: brettcannon

.github/release_plan.md

@@ -1,8 +1,9 @@
-# Monday, XXX
+# Week of Monday, XXX
 
 - [ ] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones)
 - [ ] Go through telemetry for GDPR
 - [ ] Go through all [merged pull requests](https://github.com/Microsoft/vscode-python/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged) and add the [`validate fix` label](https://github.com/Microsoft/vscode-python/labels/validate%20fix) as appropriate as well as checking for news entries
+- [ ] Triage [unverified issues](https://github.com/Microsoft/vscode-python/labels/needs%20verification)
 
 ## Planning
 - [ ] Evaluate if TypeScript usage needs updating to sync with VS Code's usage
@@ -12,21 +13,23 @@
 - [ ] Make sure all issues for this [milestone](https://github.com/Microsoft/vscode-python/milestones) are assigned
 - [ ] Close issues that have [needed more info](https://github.com/Microsoft/vscode-python/issues?q=is%3Aopen+label%3A%22needs+more+info%22+sort%3Aupdated-asc) for over a month
 
-# Monday, XXX
+# Week of Monday, XXX
 
 - [ ] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones)
 - [ ] Go through telemetry for GDPR
 - [ ] Go through all [merged pull requests](https://github.com/Microsoft/vscode-python/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged) and add the [`validate fix` label](https://github.com/Microsoft/vscode-python/labels/validate%20fix) as appropriate as well as checking for news entries
+- [ ] Triage [unverified issues](https://github.com/Microsoft/vscode-python/labels/needs%20verification)
 
 ## Planning
 - [ ] Check if there have been no performance regressions
 - [ ] Read through [VS Code's iteration plan](https://github.com/Microsoft/vscode/labels/iteration-plan) (it may still be a [draft](https://github.com/Microsoft/vscode/labels/iteration-plan-draft))
 
-# Monday, XXX
+# Week of Monday, XXX
 
 - [ ] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones)
 - [ ] Go through telemetry for GDPR
 - [ ] Go through all [merged pull requests](https://github.com/Microsoft/vscode-python/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged) and add the [`validate fix` label](https://github.com/Microsoft/vscode-python/labels/validate%20fix) as appropriate as well as checking for news entries
+- [ ] Triage [unverified issues](https://github.com/Microsoft/vscode-python/labels/needs%20verification)
 
 ## Legal
 - [ ] Announce the lock-down of dependencies for this release
@@ -37,12 +40,13 @@
 - [ ] Announce the beta [development build](https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build) (along with how to help [validate fixes](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22validate+fix%22+is%3Aclosed))
 - [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs)
 
-# Monday, XXX
+# Week of Monday, XXX
 
 - [ ] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones)
 - [ ] Go through telemetry for GDPR
 - [ ] Merge any last-minute [pull requests](https://github.com/Microsoft/vscode-python/pulls)
 - [ ] Go through all [merged pull requests](https://github.com/Microsoft/vscode-python/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged) and add the [`validate fix` label](https://github.com/Microsoft/vscode-python/labels/validate%20fix) as appropriate as well as checking for news entries
+- [ ] Triage [unverified issues](https://github.com/Microsoft/vscode-python/labels/needs%20verification)
 
 ## Prep for the release candidate
 - [ ] Announce feature freeze
@@ -59,8 +63,6 @@
 - [ ] Make sure no extraneous files are being included in the `.vsix` file (make sure to check for hidden files)
 - [ ] Make sure the [appropriate pull requests](https://github.com/microsoft/vscode-docs/pulls) for the [documentation](https://code.visualstudio.com/docs/python/python-tutorial) -- including the [WOW](https://code.visualstudio.com/docs/languages/python) page -- are ready
 
-# Wednesday, XXX (hopefully 😉)
-
 ## Release
 - [ ] Update the [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) (including the names of external contributors & projects)
 - [ ] Update the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) number to be final
@@ -72,13 +74,13 @@
 - [ ] Publish the [blog](http://aka.ms/pythonblog) post
 - [ ] Create a [release](https://github.com/Microsoft/vscode-python/releases) on GitHub (which creates an appropriate git tag)
 
-## Prep for the next release
+## Prep for the _next_ release
 - [ ] Bump the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) number to the next `alpha`
 - [ ] Make sure the next **two** [milestones](https://github.com/Microsoft/vscode-python/milestones) exist
 - [ ] Lift the feature freeze
 - [ ] Create a new [release plan](https://github.com/Microsoft/vscode-python/labels/release%20plan)
 
-## Clean up after this release
+## Clean up after _this_ release
 - [ ] Clean up any straggling [fixed issues needing validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22validate+fix%22+is%3Aclosed)
 - [ ] Close the (now) old [milestone](https://github.com/Microsoft/vscode-python/labels/release%20plan)
 - [ ] Delete the previous releases' [branch](https://github.com/Microsoft/vscode-python/branches)