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
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
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> endgame champion
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
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
Monday
Tuesday
verification-needed
oron-testplan
labelWednesday
Thursday
Friday
stable
build to ensure stable build is green endgame championinsider
builds endgame championrelease/<x.y>
after all expected fixes are in (latest 5PM PST) endgame championrelease/<x.y>
after all expected fixes are in (latest 5PM PST) endgame championmain
is open for business 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
release/*
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. endgame championThursday - Expected release day (this may change)
sudo snap install --classic --dangerous <file>.snap
) ownerprod
deployment target endgame championgit 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 Exampleinsider
builds endgame championpackage.json
onmain
- endgame championThe text was updated successfully, but these errors were encountered: