# Monday, May 07 - [x] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones) - [x] Go through telemetry for GDPR - [x] 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 ## Planning - [x] Evaluate if TypeScript usage needs updating to sync with VS Code's usage - [x] Evaluate [projects](https://github.com/Microsoft/vscode-python/projects) & [`meta` issues](https://github.com/Microsoft/vscode-python/labels/meta) - [x] Go through [`needs PR` issues](https://github.com/Microsoft/vscode-python/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3A%22needs+PR%22+-label%3A%22help+wanted%22+-label%3A%22good+first+issue%22+no%3Amilestone) to see if there's anything we want to add to this milestone - [x] Finalize the initial set of issues for the [milestone](https://github.com/Microsoft/vscode-python/milestones) - [x] Make sure all issues for this [milestone](https://github.com/Microsoft/vscode-python/milestones) are assigned - [x] 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, May 14 - [x] Be too busy to do anything because we're [sprinting at PyCon US](https://us.pycon.org/2018/community/sprints/) 😉 # Monday, May 21 - [x] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones) - [x] Go through telemetry for GDPR - [x] 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 ## Planning - [x] Check if there have been no performance regressions - [x] 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)) ## Legal - [x] Announce the lock-down of dependencies for this release - [x] Notify CELA of all changes to the [repository](https://github.com/Microsoft/vscode-python/tree/master/pythonFiles) and [distribution dependencies](https://github.com/Microsoft/vscode-python/blob/master/package.json) ## Release a beta version for testing - [x] Update the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) to be a `beta` & update the [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) - [x] 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)) - [x] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs) # Monday, May 28 - [x] Review the state of the current [milestone](https://github.com/Microsoft/vscode-python/milestones) - [x] Go through telemetry for GDPR - [x] Merge any last-minute [pull requests](https://github.com/Microsoft/vscode-python/pulls) - [x] 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 ## Prep for the release candidate - [x] Announce feature freeze - [x] Make sure the [repo](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) and [distribution TPNs](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) have been updated appropriately ## Test the release candidate code - [x] Update the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) to be an `rc` & update the [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) - [x] Announce the release candidate [development build](https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build) - [x] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs) - [x] Begin drafting a [blog](http://aka.ms/pythonblog) post ## Prep the release - [x] Ensure all new feature usages are tracked via telemetry - [x] Make sure no extraneous files are being included in the `.vsix` file (make sure to check for hidden files) - [x] 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, May 30 (hopefully 😉) ## Release - [x] Update the [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) (including the names of external contributors & projects) - [x] Update the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) number to be final - [x] Make sure [CI](https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md) is passing - [x] Create the `release-` [branch](https://github.com/Microsoft/vscode-python/branches) - [x] Generate final `.vsix` file from the `release-` branch - [x] Upload the final `.vsix` file to the [marketplace](https://marketplace.visualstudio.com/items?itemName=ms-python.python) - [x] Publish [documentation](https://code.visualstudio.com/docs/python/python-tutorial) [changes](https://github.com/microsoft/vscode-docs/pulls) - [x] Publish the [blog](http://aka.ms/pythonblog) post - [x] Create a [release](https://github.com/Microsoft/vscode-python/releases) on GitHub (which creates an appropriate git tag) ## Prep for the next release - [x] Bump the [version](https://github.com/Microsoft/vscode-python/blob/master/package.json) number to the next `alpha` - [x] Make sure the next **two** [milestones](https://github.com/Microsoft/vscode-python/milestones) exist - [x] Lift the feature freeze - [x] Create a new [release plan](https://github.com/Microsoft/vscode-python/labels/release%20plan) ## Clean up after this release - [x] Clean up any straggling [fixed issues needing validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22validate+fix%22+is%3Aclosed) - [x] Close the (now) old [milestone](https://github.com/Microsoft/vscode-python/labels/release%20plan) - [x] Delete the previous releases' [branch](https://github.com/Microsoft/vscode-python/branches)
Monday, May 07
validate fixlabel as appropriate as well as checking for news entriesPlanning
metaissuesneeds PRissues to see if there's anything we want to add to this milestoneMonday, May 14
Monday, May 21
validate fixlabel as appropriate as well as checking for news entriesPlanning
Legal
Release a beta version for testing
beta& update the changelogMonday, May 28
validate fixlabel as appropriate as well as checking for news entriesPrep for the release candidate
Test the release candidate code
rc& update the changelogPrep the release
.vsixfile (make sure to check for hidden files)Wednesday, May 30 (hopefully 😉)
Release
release-branch.vsixfile from therelease-branch.vsixfile to the marketplacePrep for the next release
alphaClean up after this release