You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[ ] Announce the feature freeze on both Teams and e-mail, leave enough time for teams to surface any last minute issues that need to get in before freeze. Make sure debugger and Language Server teams are looped in as well.
5
+
-[ ] Announce the feature freeze on both Teams and e-mail, leave enough time for teams to surface any last minute issues that need to get in before freeze. Make sure debugger and Language Server teams are looped in as well.
6
6
7
7
# Release candidate (Monday, XXX XX)
8
8
9
-
-[ ] Update `main` for the release
10
-
-[ ] Change the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) to the next **even** number (🤖)
11
-
-[ ]Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) is up-to-date (🤖)
12
-
-[ ]Check `pypi.org` and update the version of `debugpy`in `install_debugpy.py` if necessary.
13
-
-[ ]Update `languageServerVersion` in `package.json` to point to the latest version of the [Language Server](https://github.com/Microsoft/python-language-server). Check with the language server team if this needs updating (🤖)
14
-
-[ ]Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Distribution.txt) by using https://tools.opensource.microsoft.com/notice (Notes for this process are in the Team OneNote under Python VS Code → Dev Process → Third-Party Notices / TPN file)
15
-
-[ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Repository.txt) as appropriate. This file is manually edited so you can check with the teams if anything needs to be added here.
16
-
-[ ] Merge pull request into `main`
17
-
-[ ] Create the [`release` branch](https://github.com/microsoft/vscode-python/branches)
18
-
-[ ] If there are `release` branches that are two versions old you can delete them at this time
19
-
-[ ] Create a new `release/YYYY.minor` branch from `main`
20
-
-[ ] Create a draft [GitHub release](https://github.com/microsoft/vscode-python/releases) for the release notes (🤖)
21
-
-[ ] Update `main` post-release (🤖)
22
-
-[ ] Bump the minor version number to the next ("YYYY.[minor+1]") release in the `main` branch to an **odd** number (🤖)
23
-
- []`package.json`
24
-
- []`package-lock.json`
25
-
-[ ] Create a pull request against `main`
26
-
-[ ] Merge pull request into `main`
27
-
-[ ] Announce the code freeze is over on the same channels
28
-
-[ ] Update Component Governance (Notes are in the team OneNote under Python VS Code → Dev Process → Component Governance).
29
-
-[ ] Make sure there are no active alerts
30
-
-[ ] Manually add any repository/embedded/CG-incompatible dependencies
31
-
-[ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython)
32
-
-[ ] Begin drafting a [blog](http://aka.ms/pythonblog) post. Contact the PM team for this.
9
+
NOTE: Third Party Notices are automatically added by our build pipelines using https://tools.opensource.microsoft.com/notice.
10
+
11
+
-[ ]Update `main` for the release
12
+
-[ ]Change the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) to the next **even** number (🤖)
13
+
-[ ]Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) is up-to-date (🤖)
14
+
-[ ]Check `pypi.org` and update the version of `debugpy`in `install_debugpy.py` if necessary.
15
+
-[ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Repository.txt) as appropriate. This file is manually edited so you can check with the teams if anything needs to be added here.
16
+
-[ ] Merge pull request into `main`
17
+
-[ ] Create the [`release` branch](https://github.com/microsoft/vscode-python/branches)
18
+
-[ ] If there are `release` branches that are two versions old you can delete them at this time
19
+
-[ ] Create a new `release/YYYY.minor` branch from `main`
20
+
-[ ] Create a draft [GitHub release](https://github.com/microsoft/vscode-python/releases) for the release notes (🤖)
21
+
-[ ] Update `main` post-release (🤖)
22
+
-[ ] Bump the minor version number to the next ("YYYY.[minor+1]") release in the `main` branch to an **odd** number (🤖)
23
+
-[ ]`package.json`
24
+
-[ ]`package-lock.json`
25
+
-[ ] Create a pull request against `main`
26
+
-[ ] Merge pull request into `main`
27
+
-[ ] Announce the code freeze is over on the same channels
28
+
-[ ] Update Component Governance (Notes are in the team OneNote under Python VS Code → Dev Process → Component Governance).
29
+
-[ ] Make sure there are no active alerts
30
+
-[ ] Manually add any repository/embedded/CG-incompatible dependencies
31
+
-[ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython)
32
+
-[ ] Begin drafting a [blog](http://aka.ms/pythonblog) post. Contact the PM team for this.
33
33
34
34
# Release (Wednesday, XXX XX)
35
35
36
36
## Preparation
37
37
38
-
-[ ] 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
39
-
-[ ] Final updates to the `release-YYYY.minor` branch
40
-
-[ ] Create a branch against `release-YYYY.minor` for a pull request
41
-
-[ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) to remove the `-rc` (🤖)
42
-
-[ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) is up-to-date (the only update should be the version number if `package-lock.json` has been kept up-to-date) (🤖)
43
-
-[ ] Update [`ThirdPartyNotices-Distribution.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Distribution.txt) by using https://tools.opensource.microsoft.com/notice (🤖; see team notes)
44
-
-[ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Repository.txt) manually if necessary
45
-
-[ ] Create pull request against `release/YYYY.minor` (🤖)
46
-
-[ ] Merge pull request into `release/YYYY.minor`
38
+
-[ ] 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
39
+
-[ ] Final updates to the `release-YYYY.minor` branch
40
+
-[ ] Create a branch against `release-YYYY.minor` for a pull request
41
+
-[ ] Update the version in [`package.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) to remove the `-rc` (🤖)
42
+
-[ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/main/package.json) is up-to-date (the only update should be the version number if `package-lock.json` has been kept up-to-date) (🤖)
43
+
-[ ] Update [`ThirdPartyNotices-Repository.txt`](https://github.com/Microsoft/vscode-python/blob/main/ThirdPartyNotices-Repository.txt) manually if necessary
44
+
-[ ] Create pull request against `release/YYYY.minor` (🤖)
45
+
-[ ] Merge pull request into `release/YYYY.minor`
47
46
48
47
## Release
49
48
50
-
-[ ] Make sure [CI](https://github.com/microsoft/vscode-python/actions?query=workflow%3A%22Insiders+Build%22) is passing (🤖)
51
-
-[ ] Run the CD pipeline
52
-
-[ ]Create a [GitHub release](https://github.com/microsoft/vscode-python/releases) (🤖)
-[ ]Publish the [blog](http://aka.ms/pythonblog) post
57
+
-[ ]Determine if a hotfix is needed
58
+
-[ ] Merge the release branch back into `main`. Don't overwrite the main branch version. (🤖)
60
59
61
60
## Prep for the _next_ release
62
61
63
-
-[ ] Create a new [release plan](https://raw.githubusercontent.com/microsoft/vscode-python/main/.github/release_plan.md) (🤖)
64
-
-[ ][(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) (🤖)
62
+
-[ ] Create a new [release plan](https://raw.githubusercontent.com/microsoft/vscode-python/main/.github/release_plan.md) (🤖)
63
+
-[ ][(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