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 @Yoyokrazy
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 redistribute 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. Remind team to move out or close other open issues/PRs on the milestone that they do not intend to fix this milestone.
Confirm with team extension authors when to disable continuous insider builds (includes vscode.dev publishing). The default time is Thursday EOD (Redmond) @Yoyokrazy
Fixing (self-assigned, milestone assigned)
Increased scrutiny sets in due to testing being completed. Fixes pose a much higher risk
Move open issues/PRs to the next month that can be deferred
Emphasize to the team that we want to verify as many issues as we can before the branching time, and ping team members as needed to remind them to add steps to verification-steps-needed issues @Yoyokrazy
By Thursday EOD (Redmond), branch from main and release @Yoyokrazy
Disable the continuous release by toggling the continuous release button on the top-right corner of the Builds page
Branch following repositories to release/<x.y>
vscode
vscode-distro
vscode-dev
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 team extension authors to check if all release branch changes have been published to users. If not, they need to build and manually release a new prerelease version of their extension. @Yoyokrazy
Build but don't release a stable build from release/<x.y> branch to ensure stable build is green @Yoyokrazy
Bump up the version in package.json on main - @Yoyokrazy
Create next milestone on microsoft/vscode repo and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos. @Yoyokrazy
Friday
Only candidate issues are open and assigned to 🔖milestone
candidate fixes should be made for major bugs only - to be discussed in stand-up meeting and approved
Endgame champion / authors of candidate PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders.
Satellite modules/npm packages ready, version updated, smoke tested
Check the internal iteration plan for scheduled security issues (MSRCs) to determine if a Patch Tuesday release is needed.
If no Patch Tuesday release is planned, use the Patch Tuesday E-Mail Template to let the Updates team ([email protected]) know of that fact. Please cc Monacotools on this email as the client patching team has asked us to do so. @Yoyokrazy
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. @Yoyokrazy
Cherry-pick hand-picked and reviewed changes to release/<x.y>, and close open candidate issues that have already been merged to the release branch. @Yoyokrazy
Build Insider from release/<x.y> (roughly on a daily basis) @Yoyokrazy
Endgame champion / authors of candidate PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders. team
Build but don't release stable for all platforms as new candidate issues come in @Yoyokrazy
Documentation updated
Run scripts/test-documentation.sh|bat after compiling the vscode repo, and fix any issues regarding new undocumented colors. Changes made to the vscode-docs repository must be merged to the main branch of that repository for the script to acknowledge them. False positives within the color section in vscode-known-variables.json can be moved under the others section of that file. @Yoyokrazy
Coordinate the official release timing with team and more specifically, team extension authors (ex: Jupyter and Copilot rely on VS Code release) @Yoyokrazy
Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame, though the sanity testing step alone can happen earlier if there are no new candidates. @Yoyokrazy
Wednesday/Thursday - Expected release day (this may change)
Release stable from builds page no later than 11am PT @Yoyokrazy
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 @Yoyokrazy
Request approval from another team member at the necessary step to deploy the vscode.dev build. @Yoyokrazy
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-needed
oron-testplan
labelTuesday
blocked
and status update comment in the issue.Wednesday
verification-steps-needed
issues @YoyokrazyThursday
insider
build is green @Yoyokrazyinsider
builds (includes vscode.dev publishing). The default time is Thursday EOD (Redmond) @Yoyokrazyverification-steps-needed
issues @Yoyokrazymain
and release @Yoyokrazyrelease/<x.y>
release/*
as the VS Code Branch parameter (it's the default so you shouldn't have to change anything)main
is open for business and all issues on the current iteration are candidates and that the candidate release process is to be followed.stable
build from release/<x.y> branch to ensure stable build is green @Yoyokrazypackage.json
onmain
- @Yoyokrazymicrosoft/vscode
repo and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos. @YoyokrazyFriday
candidate
fixes should be made for major bugs only - to be discussed in stand-up meeting and approvedcandidate
PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders.v<Major>_<Minor>.md
_ in this repo directoryFriday/Monday
Monday - Wednesday
release/<x.y>
, and close open candidate issues that have already been merged to the release branch. @YoyokrazyInsider
fromrelease/<x.y>
(roughly on a daily basis) @YoyokrazyInsider
@Yoyokrazycandidate
PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders. teamscripts/test-documentation.sh|bat
after compiling the vscode repo, and fix any issues regarding new undocumented colors. Changes made to the vscode-docs repository must be merged to the main branch of that repository for the script to acknowledge them. False positives within thecolor
section invscode-known-variables.json
can be moved under theothers
section of that file. @YoyokrazyWednesday/Thursday - Expected release day (this may change)
main
for all platforms @Yoyokrazyrelease/x.y
for theprod
deployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions @Yoyokrazygit 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 @Yoyokrazymain
@YoyokrazyThe text was updated successfully, but these errors were encountered: