|
10 | 10 | - [ ] Announce the code freeze (not just to team but also to ptvsd and language server) |
11 | 11 | - [ ] Update master for the release |
12 | 12 | - [ ] Create a branch against `master` for a pull request |
13 | | - - [ ] Change the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) from a `-dev` suffix to `-rc` |
14 | | - - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date |
| 13 | + - [ ] Change the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) from a `-dev` suffix to `-rc` (🤖) |
| 14 | + - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date (🤖) |
15 | 15 | - [ ] Update `requirements.txt` to point to latest release version of [ptvsd](https://github.com/microsoft/ptvsd). |
16 | 16 | - [ ] Update `languageServerVersion` in `package.json` to point to the latest version (???) of [the Language Server](https://github.com/Microsoft/python-language-server). |
17 | | - - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) |
| 17 | + - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) (🤖) |
18 | 18 | - [ ] Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news --final --update CHANGELOG.md | code-insiders -`) |
19 | 19 | - [ ] Copy over the "Thanks" section from the previous release |
20 | 20 | - [ ] Make sure the "Thanks" section is up-to-date (e.g. compare to versions in requirements.json) |
|
31 | 31 | + ask the package maintainer (e.g. via github) |
32 | 32 | + ask CELA |
33 | 33 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) as appropriate |
34 | | - - [ ] Create a pull request against `master` |
| 34 | + - [ ] Create a pull request against `master` (🤖) |
35 | 35 | - [ ] Merge pull request into `master` |
36 | 36 | - [ ] Update the [`release` branch](https://github.com/microsoft/vscode-python/branches) |
37 | 37 | - [ ] (if necessary) Request from a repo admin that the branch be un-"protected" |
38 | 38 | - [ ] Delete the `release` branch in the repo |
39 | 39 | - [ ] Create a new `release` branch from `master` |
40 | 40 | - (alternately, force-push the master branch to the GitHub "release" branch) |
41 | 41 | - [ ] (if necessary) Request that the branch be set anew as "protected" |
42 | | -- [ ] Update master post-release |
| 42 | +- [ ] Update master post-release (🤖) |
43 | 43 | - [ ] Bump the version number to the next monthly ("YYYY.M.0-dev") release in the `master` branch |
44 | 44 | - [ ] `package.json` |
45 | 45 | - [ ] `package-lock.json` |
|
49 | 49 | - [ ] Update [Component Governance](https://dev.azure.com/ms/vscode-python/_componentGovernance) (Click on "microsoft/vscode-python" on that page) |
50 | 50 | - [ ] Provide details for any automatically detected npm dependencies |
51 | 51 | - [ ] Manually add any repository dependencies |
52 | | -- [ ] GDPR bookkeeping (@brettcannon) |
| 52 | +- [ ] GDPR bookkeeping (@brettcannon) (🤖) |
53 | 53 | - [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython) |
54 | 54 | + new features |
55 | 55 | + settings changes |
|
65 | 65 | - [ ] 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 |
66 | 66 | - [ ] final updates to the `release` branch |
67 | 67 | - [ ] Create a branch against `release` for a pull request |
68 | | - - [ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) |
69 | | - - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date (the only update should be the version number if `package-lock.json` has been kept up-to-date) |
70 | | - - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) |
| 68 | + - [ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) (🤖) |
| 69 | + - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date (the only update should be the version number if `package-lock.json` has been kept up-to-date) (🤖) |
| 70 | + - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) (🤖) |
71 | 71 | - [ ] Update version and date for the release section |
72 | 72 | - [ ] Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) and copy-and-paste new entries (typically `python news --final | code-insiders -`; quite possibly nothing new to add) |
73 | | - - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) by running [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn) (typically `python tpn --npm package-lock.json --npm-overrides package.datascience-ui.dependencies.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`; quite possible there will be no change) |
| 73 | + - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) by running [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn) (typically `python tpn --npm package-lock.json --npm-overrides package.datascience-ui.dependencies.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`; quite possible there will be no change) (🤖) |
74 | 74 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) manually if necessary |
75 | | - - [ ] Create pull request against `release` |
| 75 | + - [ ] Create pull request against `release` (🤖) |
76 | 76 | - [ ] Merge pull request into `release` |
77 | 77 | - [ ] Make sure component governance is happy |
78 | 78 |
|
|
86 | 86 | - [ ] Publish [documentation changes](https://github.com/Microsoft/vscode-docs/pulls?q=is%3Apr+is%3Aopen+label%3Apython) |
87 | 87 | - [ ] Publish the [blog](http://aka.ms/pythonblog) post |
88 | 88 | - [ ] Determine if a hotfix is needed |
89 | | -- [ ] Merge `release` back into `master` |
| 89 | +- [ ] Merge `release` back into `master` (🤖) |
90 | 90 |
|
91 | 91 | ## Clean up after _this_ release |
92 | | -- [ ] Go through [`info needed` issues](https://github.com/Microsoft/vscode-python/issues?q=is%3Aopen+label%3A%22info+needed%22+-label%3A%22data+science%22+sort%3Aupdated-asc) and close any that have no activity for over a month |
93 | | -- [ ] GDPR bookkeeping |
| 92 | +- [ ] Go through [`info needed` issues](https://github.com/Microsoft/vscode-python/issues?q=is%3Aopen+label%3A%22info+needed%22+-label%3A%22data+science%22+sort%3Aupdated-asc) and close any that have no activity for over a month (🤖) |
| 93 | +- [ ] GDPR bookkeeping (🤖) |
94 | 94 |
|
95 | 95 | ## Prep for the _next_ release |
96 | | -- [ ] Create a new [release plan](https://raw.githubusercontent.com/microsoft/vscode-python/master/.github/release_plan.md) |
97 | | -- [ ] [(Un-)pin](https://help.github.com/en/articles/pinning-an-issue-to-your-repository) [release plan issues](https://github.com/Microsoft/vscode-python/labels/release%20plan) |
| 96 | +- [ ] Create a new [release plan](https://raw.githubusercontent.com/microsoft/vscode-python/master/.github/release_plan.md) (🤖) |
| 97 | +- [ ] [(Un-)pin](https://help.github.com/en/articles/pinning-an-issue-to-your-repository) [release plan issues](https://github.com/Microsoft/vscode-python/labels/release%20plan) (🤖) |
0 commit comments