|
4 | 4 | - [ ] Create a milestone with the issues that are fixed by this release
|
5 | 5 | - [ ] Update `master` for the release
|
6 | 6 | - [ ] Update hardcoded latest version for `dlv-dap` and `gopls`
|
| 7 | + - [ ] Update [`CHANGELOG.md`](https://github.com/golang/vscode-go/blob/master/CHANGELOG.md) |
| 8 | + - [ ] Make sure the "Thanks" section is up-to-date |
| 9 | + - [ ] Check the Markdown rendering to make sure everything looks good |
7 | 10 | - [ ] Update `release` for the release
|
8 | 11 | - [ ] Create a branch against `release` for a pull request
|
9 | 12 | - [ ] Merge changes from `master` to prepare for the release
|
10 | 13 | - [ ] Change the version in [`package.json`](https://github.com/golang/vscode-go/blob/master/package.json) from a `-dev` suffix
|
11 | 14 | - [ ] Run `npm install` to make sure [`package-lock.json`](https://github.com/golang/vscode-go/blob/master/package.json) is up-to-date
|
12 | 15 | - [ ] Update the license file (`$ tools/license.sh; mv LICENSE.prod LICENSE`)
|
13 |
| - - [ ] Update [`CHANGELOG.md`](https://github.com/golang/vscode-go/blob/master/CHANGELOG.md) |
14 |
| - - [ ] Make sure the "Thanks" section is up-to-date |
15 |
| - - [ ] Check the Markdown rendering to make sure everything looks good |
16 | 16 | - [ ] Check the [Long Tests status](https://github.com/golang/vscode-go/actions?query=workflow%3A%22Long+Tests%22) is green. Otherwise, fix the tests, send cls for review, submit them, and repeat.
|
17 | 17 | - [ ] Perform manual [smoke tests]( https://github.com/golang/vscode-go/blob/master/docs/smoke-test.md)
|
18 | 18 | - [ ] Create new version tag for X.XX.X-rc.1 at gerrit’s vscode-go [repo management page](https://go-review.googlesource.com/admin/repos/vscode-go,tags)
|
19 | 19 | - [ ] Go to the release page https://github.com/golang/vscode-go/releases and check if the new release candidate is up. If necessary, you can manually edit the comment by clicking the “Edit” button. Don’t mutate uploaded vsix.
|
20 | 20 | - [ ] Ask editor team and contributors to this release to test the release candidate
|
21 | 21 |
|
22 | 22 | # Release Candidate >1 (if necessary)
|
23 |
| -- ] Fix any bugs on `master` and cherry pick changes to `release |
| 23 | +- [ ] Fix any bugs on `master` and cherry pick changes to `release |
24 | 24 | - [ ] Create new version tag for X.XX.X-rc.1 at gerrit’s vscode-go [repo management page](https://go-review.googlesource.com/admin/repos/vscode-go,tags)
|
25 | 25 | - [ ] Go to the release page https://github.com/golang/vscode-go/releases and check if the new release candidate is up. If necessary, you can manually edit the comment by clicking the “Edit” button. Don’t mutate uploaded vsix.
|
26 | 26 | - [ ] Ask editor team and contributors to this release to test the release candidate
|
|
36 | 36 | - [ ] Bump the version number to the next monthly ("X.XX.X-dev") release in the `master` branch
|
37 | 37 | - [ ] `package.json`
|
38 | 38 | - [ ] `package-lock.json`
|
39 |
| - - [ ] Cherry pick CHANGELOG.md back to master |
0 commit comments