|
21 | 21 | - [ ] Touch up news entries (e.g. add missing periods) |
22 | 22 | - [ ] Check the Markdown rendering to make sure everything looks good |
23 | 23 | - [ ] Add any relevant news entries for ptvsd and the language server if they were updated |
24 | | - - [ ] 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`) |
25 | | - * for each failure: |
26 | | - 1. go to the repo (from link on NPM page) and look for the license there |
27 | | - 1. copy the text from the failure into `tpn/distribution.toml` |
28 | | - 1. fill in the license found in the package's repo |
29 | | - * if there is no license in a package's repo then do one of the following: |
30 | | - + check the NPM metadata and fill in the corresponding license from the OSI site |
31 | | - + ask the package maintainer (e.g. via github) |
32 | | - + ask CELA |
| 24 | + - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) by using https://tools.opensource.microsoft.com/notice (see team notes) |
33 | 25 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) as appropriate |
34 | 26 | - [ ] Create a pull request against `master` (🤖) |
35 | 27 | - [ ] Merge pull request into `master` |
|
48 | 40 | - [ ] Update [Component Governance](https://dev.azure.com/ms/vscode-python/_componentGovernance) (Click on "microsoft/vscode-python" on that page) |
49 | 41 | - [ ] Provide details for any automatically detected npm dependencies |
50 | 42 | - [ ] Manually add any repository dependencies |
51 | | -- [ ] GDPR bookkeeping (@brettcannon) (🤖) |
| 43 | +- [ ] GDPR bookkeeping (@brettcannon) (🤖; see team notes) |
52 | 44 | - [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython) |
53 | 45 | + new features |
54 | 46 | + settings changes |
|
69 | 61 | - [ ] Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md) (🤖) |
70 | 62 | - [ ] Update version and date for the release section |
71 | 63 | - [ ] 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) |
72 | | - - [ ] 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) (🤖) |
| 64 | + - [ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt) by using https://tools.opensource.microsoft.com/notice (🤖; see team notes) |
73 | 65 | - [ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt) manually if necessary |
74 | 66 | - [ ] Create pull request against `release` (🤖) |
75 | 67 | - [ ] Merge pull request into `release` |
|
0 commit comments