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. @mjbvz
When done fixing/verifying and there are changes since last build at the end of day PT
Build and manually release Insider from release/<x.y> @mjbvz
Localization: Run Update VS Code Branch build with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) @mjbvz
Create a tag (make sure you pull the release branch first): git tag <x.y.z>
Push the tag: git push origin <x.y.z>
Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links Example
mjbvz commentedAug 23, 2022
•
edited
Monday
verification-neededoron-testplanlabelTuesday
Wednesday
Thursday
Friday
stablebuild to ensure stable build is green @mjbvzinsiderbuilds @mjbvzrelease/<x.y>after all expected fixes are in (latest 5PM PST) @mjbvzrelease/<x.y>after all expected fixes are in (latest 5PM PST) @mjbvzmainis open for business @mjbvzcandidate)v<Major>_<Minor>.mdin 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-vscerelease/*as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) @mjbvzFriday/Monday
Monday - Wednesday
release/<x.y>@mjbvzInsiderfromrelease/<x.y>@mjbvzInsider@mjbvzscripts/test-documentation.sh|batand add file or fix issues if there are new colors that are not documented. @mjbvzWednesday/Thursday - Expected release day (this may change)
sudo snap install --classic --dangerous <file>.snap) ownerproddeployment target. Request approval from another team member at the necessary step. @mjbvzgit tag <x.y.z>git push origin <x.y.z>... > Create Release. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links Exampleinsiderbuilds @mjbvzpackage.jsononmain- @mjbvzThe text was updated successfully, but these errors were encountered: