-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
August 2022 Endgame #158841
Labels
endgame-plan
VS Code - Next release plan for endgame
Comments
16 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Monday
verification-needed
oron-testplan
labelTuesday
Wednesday
Thursday
Friday
stable
build to ensure stable build is green @mjbvzinsider
builds @mjbvzrelease/<x.y>
after all expected fixes are in (latest 5PM PST) @mjbvzrelease/<x.y>
after all expected fixes are in (latest 5PM PST) @mjbvzmain
is open for business @mjbvzcandidate
)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) @mjbvzFriday/Monday
Monday - Wednesday
release/<x.y>
@mjbvzInsider
fromrelease/<x.y>
@mjbvzInsider
@mjbvzscripts/test-documentation.sh|bat
and 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
)prod
deployment 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 Exampleinsider
builds @mjbvzpackage.json
onmain
- @mjbvzThe text was updated successfully, but these errors were encountered: