|
3 | 3 | - [ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) |
4 | 4 | - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date |
5 | 5 | - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) |
6 | | - - Create a new section for this release |
7 | | - - Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news | code-insiders -`) |
8 | | - - Touch up news entries (and corresponding news entry files) |
9 | | - - Copy over the "Thanks" section from the previous release |
| 6 | + - [ ] Create a new section for this release |
| 7 | + - [ ] Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news | code-insiders -`) |
| 8 | + - [ ] Touch up news entries (and corresponding news entry files) |
| 9 | + - [ ] Copy over the "Thanks" section from the previous release |
10 | 10 | - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) |
11 | | - - Run [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn) (typically `python tpn --npm package-lock.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`) |
12 | | - - Register any Python changes with [OSPO](https://opensource.microsoft.com/) |
| 11 | + - [ ] Run [`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`) |
| 12 | + - [ ] Register any Python changes with [OSPO](https://opensource.microsoft.com/) |
13 | 13 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) and register any changes with OSPO |
14 | 14 | - [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython) |
| 15 | +- [ ] Check that component governance is happy (requires beta PR to have been merged) |
15 | 16 |
|
16 | 17 |
|
17 | 18 | # Release candidate (Monday before release) |
18 | 19 |
|
19 | | -- [ ] Ensure all new feature usages are tracked via telemetry |
| 20 | +- [ ] Ensure all new features are tracked via telemetry |
| 21 | +- [ ] Announce a code freeze |
| 22 | +- [ ] Create a branch against `master` for a pull request |
20 | 23 | - [ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) |
21 | 24 | - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) is up-to-date |
22 | 25 | - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) |
23 | | - - Update version and date for the release section |
24 | | - - Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news --final | code-insiders -`) |
25 | | - - Touch up news entries (and corresponding news entry files) |
26 | | - - Check that the "Thanks" section is up-to-date |
| 26 | + - [ ] Update version and date for the release section |
| 27 | + - [ ] Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news --final | code-insiders -`; the `--final` flag is on purpose as no more changes are expected) |
| 28 | + - [ ] Touch up news entries (and corresponding news entry files) |
| 29 | + - [ ] Check that the "Thanks" section is up-to-date |
27 | 30 | - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) |
28 | | - - Run [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn) (typically `python tpn --npm package-lock.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`) |
29 | | - - Register any Python changes with [OSPO](https://opensource.microsoft.com/) |
| 31 | + - [ ] Run [`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`) |
| 32 | + - [ ] Register any Python changes with [OSPO](https://opensource.microsoft.com/) |
30 | 33 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) and register any changes with OSPO |
31 | | -- [ ] Merge into the [`release` branch](https://github.com/microsoft/vscode-python/tree/release) |
| 34 | +- [ ] Merge pull request into `master` |
| 35 | +- [ ] Delete the `release` branch in the repo |
| 36 | +- [ ] Create a new `release` branch from `master` |
| 37 | +- [ ] Bump the version number to the next release in the `master` branch |
| 38 | + - [ ] `package.json` |
| 39 | + - [ ] `package-lock.json` |
| 40 | +- [ ] Announce the code freeze is over |
32 | 41 | - [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython) |
33 | 42 | - [ ] Begin drafting a [blog](http://aka.ms/pythonblog) post |
| 43 | +- [ ] Make sure component governance is happy (requires RC PR to have been merged) |
34 | 44 |
|
35 | 45 |
|
36 | 46 | # Final (near a VS Code release) |
37 | 47 |
|
38 | 48 | ## Preparation |
39 | | -[Final PR should be against the `release` branch] |
40 | 49 |
|
41 | 50 | - [ ] 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 |
| 51 | +- [ ] Create a branch against `release` for a pull request |
42 | 52 | - [ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json) |
43 | 53 | - [ ] 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) |
44 | 54 | - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) |
45 | | - - Update version and date for the release section |
46 | | - - Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news --final | code-insiders -`) |
| 55 | + - [ ] Update version and date for the release section |
| 56 | + - [ ] Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news) (typically `python news --final | code-insiders -`) |
47 | 57 | - Check that the "Thanks" section is up-to-date |
48 | 58 | - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) |
49 | | - - Run [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn) (typically `python tpn --npm package-lock.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`) |
50 | | - - Register any Python changes with [OSPO](https://opensource.microsoft.com/) |
| 59 | + - [ ] Run [`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`) |
| 60 | + - [ ] Register any Python changes with component governance |
51 | 61 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) and register any changes with OSPO |
| 62 | +- [ ] Merge pull request into `release` |
| 63 | +- [ ] Make sure component governance is happy |
52 | 64 |
|
53 | 65 | ## Release |
54 | 66 |
|
55 | 67 | - [ ] Make sure [CI](https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md) is passing |
56 | 68 | - [ ] Generate the final `.vsix` file |
57 | 69 | - [ ] Make sure no extraneous files are being included in the `.vsix` file (make sure to check for hidden files) |
58 | 70 | - [ ] Upload the final `.vsix` file to the [marketplace](https://marketplace.visualstudio.com/items?itemName=ms-python.python) |
59 | | -- [ ] Publish [documentation](https://code.visualstudio.com/docs/python/python-tutorial) [changes](https://github.com/microsoft/vscode-docs/pulls) |
| 71 | +- [ ] Publish [documentation changes](https://github.com/microsoft/vscode-docs/pulls) |
60 | 72 | - [ ] Publish the [blog](http://aka.ms/pythonblog) post |
61 | 73 | - [ ] Create a [release](https://github.com/Microsoft/vscode-python/releases) on GitHub (which creates an appropriate git tag) |
62 | 74 | - [ ] Determine if a hotfix is needed |
|
67 | 79 | - [ ] Create a new [release plan](https://github.com/Microsoft/vscode-python/edit/master/.github/release_plan.md) |
68 | 80 |
|
69 | 81 | ## Clean up after _this_ release |
70 | | -- [ ] Clean up any straggling [fixed issues needing validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22validate+fix%22+is%3Aclosed) |
71 | | -- [ ] Go through [`needs more info` issues](https://github.com/Microsoft/vscode-python/issues?q=is%3Aopen+label%3A%22needs+more+info%22+sort%3Aupdated-asc) and close any that have no activity for over a month |
| 82 | +- [ ] Clean up any straggling [fixed issues needing validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22validate+fix%22) |
| 83 | +- [ ] Go through [`needs more info` issues](https://github.com/Microsoft/vscode-python/issues?q=is%3Aopen+label%3A%22info+needed%22+sort%3Acreated-asc) and close any that have no activity for over a month |
0 commit comments