Skip to content

Commit f5ba752

Browse files
authored
Link to the release plan on how to do a release
1 parent 6b5df54 commit f5ba752

1 file changed

Lines changed: 1 addition & 27 deletions

File tree

CONTRIBUTING.md

Lines changed: 1 addition & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -250,33 +250,7 @@ Overall steps for releasing are covered in the
250250

251251
### Building a release
252252

253-
To create a release _build_, the following steps should be followed:
254-
255-
1. Update the version in
256-
[`package.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json)
257-
1. Run `npm install` to make sure
258-
[`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package.json)
259-
is up-to-date (the only update should be the version number if
260-
`package-lock.json` has been kept up-to-date otherwise)
261-
1. Update [`CHANGELOG.md`](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md)
262-
- If this is the first release **after** a final release, then create a new section,
263-
otherwise update the version and date in section header
264-
- Run [`news`](https://github.com/Microsoft/vscode-python/tree/master/news)
265-
(typically `python3 news | code-insiders -`; add `--final` if this
266-
is a final release)
267-
- Touch up news entries (if a non-final release then also touch up news entry
268-
files as appropriate)
269-
- Check that the "thank you" section is up-to-date
270-
1. Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Distribution.txt)
271-
- Run [`tpn`](https://github.com/Microsoft/vscode-python/tree/master/tpn)
272-
(typically
273-
`python3 tpn --npm package-lock.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt`)
274-
- Register any version changes or new dependencies with [OSPO](https://opensource.microsoft.com/)
275-
1. Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/master/ThirdPartyNotices-Repository.txt)
276-
and register any changes with OSPO
277-
278-
Once the above changes have been merged into `master` you can then download the
279-
development build `.vsix` for releasing.
253+
To create a release _build_, follow the steps outlined in the [release plan](https://github.com/Microsoft/vscode-python/labels/release%20plan) (which has a [template](https://github.com/Microsoft/vscode-python/blob/master/.github/release_plan.md)).
280254

281255
## Development Build
282256

0 commit comments

Comments
 (0)