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
Create test plan items following the template here by 6pm PT
Remind the team that TPIs should be written so that anyone can test. If this is not feasible, then TPI authors should assign specific testers Aiday Marlen Kyzy (@aiday-mar)
Tuesday should be dedicated exclusively to testing activities. Our goal is to ensure the completion of all Test Plan Items (TPIs) and subsequently proceed with the verification phase. Fixes or commits should be refrained from unless there are exceptional circumstances such as blocked TPIs or build-related issues. On Tuesday Redmond EOD, only blocked TPIs should remain open with a corresponding label blocked and status update comment in the issue.
Redmond members commence testing the TPIs authored by Zurich members, enabling them to address any feedback on the following day.
These remaining TPIs should be the ones that are currently blocked. Discuss during the standup and redistrubute assignments based on the TPI owner and the test coverage. For instance, if a TPI is owned by a member from Zurich and has not undergone sufficient testing, it will be reassigned to one of the Zurich team members.
Remind team members to triage issues found in testing and assign major issues that they intend to fix to the current milestone
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)
Announce main is open for business and all issues on the current iteration are candidates and that the candidate release process is to be followed.
Build and manually release Insider from release/<x.y> branch for Code
Build and manually release Insider from release/<x.y> branch for vscode.dev (if there were vscode.dev candidates)
Remind the team: if they are going to be OOF for more than five days during the next iteration, assign someone to look out for critical issues in their feature areas and fix them if necessary. This helps with bug identification and fixing for recovery releases. Aiday Marlen Kyzy (@aiday-mar)
Trigger the vscode.dev Deploy pipeline for release/x.y for the prod deployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions Aiday Marlen Kyzy (@aiday-mar)
Request approval from another team member at the necessary step to deploy the vscode.dev build. Aiday Marlen Kyzy (@aiday-mar)
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
verification-neededoron-testplanlabelTuesday
blockedand status update comment in the issue.Wednesday
Thursday
insiderbuild Aiday Marlen Kyzy (@aiday-mar)insiderbuilds (includes vscode.dev publishing) Aiday Marlen Kyzy (@aiday-mar)mainand release Aiday Marlen Kyzy (@aiday-mar)release/<x.y>release/*as the VS Code Branch parameter (it's the default so you shouldn't have to change anything)mainis open for business and all issues on the current iteration are candidates and that the candidate release process is to be followed.stablebuild from release/<x.y> branch to ensure stable build is green Aiday Marlen Kyzy (@aiday-mar)package.jsononmain- Aiday Marlen Kyzy (@aiday-mar)Friday
candidate)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,vscode-pylint,vscode-black-formatter,vscode-isort,lsprotocol,vscode-flake8,vscode-autopep8,vscode-python-tools-extension-template,vscode-mypy,vscode-python-debuggerFriday/Monday
Monday - Wednesday
release/<x.y>Aiday Marlen Kyzy (@aiday-mar)Insiderfromrelease/<x.y>Aiday Marlen Kyzy (@aiday-mar)InsiderAiday Marlen Kyzy (@aiday-mar)scripts/test-documentation.sh|batand add file or fix issues if there are new colors that are not documented. Aiday Marlen Kyzy (@aiday-mar)Wednesday/Thursday - Expected release day (this may change)
mainfor all platforms Aiday Marlen Kyzy (@aiday-mar)release/x.yfor theproddeployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions Aiday Marlen Kyzy (@aiday-mar)git 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 Aiday Marlen Kyzy (@aiday-mar)