[x] Fixing (scrutiny sets in once branched - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
[ ] All release notes updated
release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
[ ] @aeschli
[ ] @alexdima
[x] @alexr00
[ ] @andreamah
[ ] @bpasero
[ ] @chrmarti
[x] @connor4312
[x] @dbaeumer
[ ] @deepak1556
[ ] @eamodio
[x] @egamma
[x] @hediet
[x] @isidorn
[ ] @JacksonKearl
[ ] @joaomoreno
[ ] @jrieken
[ ] @kieferrm
[x] @lramos15
[ ] @lszomoru
[x] @meganrogge
[ ] @mjbvz
[ ] @rebornix
[x] @roblourens
[x] @rzhao271
[x] @sandy081
[ ] @sbatten
[x] @stuartleeks
[x] @tylerleonhardt
[ ] @tyriar
[x] @weinand
[x] Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the endgame champion can generate the pull request acknowledgment for all repositories at once. endgame champion
[x] Acknowledge issue trackers from the community @lszomoru
[x] Add notable fixes to the release notes all
When done fixing/verifying and there are changes since last build at the end of day PT
[x] Build and manually release Insider from release/<x.y> endgame champion
[x] Bump up the version in package.json on main - endgame champion
[x] Announce main is open for business endgame champion
[x] Localization: Run Update VS Code Branch in the vscode-loc-drop repo with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) endgame champion
Friday/Monday
[x] Polish release notes redmond
[x] Fixing (only critical bugs - no string changes)
[x] Publish Localization language pack @tylerleonhardt
[x] Publish to stable endgame champion
[x] Create an official release endgame champion
[x] Create a tag: git tag <x.y.z>
[x] Push the tag: git push origin <x.y.z>
[x] Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Example
Monday
Tuesday
verification-needed
oron-testplan
labelWednesday
Thursday
Friday
insider
builds endgame championrelease/<x.y>
endgame championcandidate
)v<Major>_<Minor>.md
in this repo directorydebug-adapter-protocol
,inno-updater
,jsonc-parser
,language-server-protocol
,lsif-node
,vscode
,vscode-codicons
,vscode-css-languageservice
,vscode-debugadapter-node
,vscode-dev-containers
,vscode-docs
,vscode-emmet-helper
,vscode-eslint
,vscode-extension-samples
,vscode-generator-code
,vscode-hexeditor
,vscode-html-languageservice
,vscode-js-debug
,vscode-js-debug-companion
,vscode-js-profile-visualizer
,vscode-jshint
,vscode-json-languageservice
,vscode-languageserver-node
,vscode-livepreview
,vscode-loader
,vscode-lsif-extension
,vscode-node-debug
,vscode-node-debug2
,vscode-pull-request-github
,vscode-recipes
,vscode-references-view
,vscode-textmate
,vscode-vsce
package.json
onmain
- endgame championmain
is open for business endgame championrelease/*
as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) endgame championFriday/Monday
Monday - Wednesday
release/<x.y>
endgame championInsider
fromrelease/<x.y>
endgame championInsider
endgame championscripts/test-documentation.sh|bat
and add file or fix issues if there are new colors that are not documented.Wednesday/Thursday - Expected release day (this may change)
sudo snap install --classic --dangerous <file>.snap
) @deepak1556git tag <x.y.z>
git push origin <x.y.z>
... > Create Release
. Use the correct title and description from our release notes. Exampleinsider
builds endgame champion