1.130.0 Endgame

[aeschli]

Endgame guide

Before Monday 6AM Zurich time

@team:

• Update endgame availability
• Test plan items created
• Milestone only has TPIs. All other issues need to be closed
• All closed issues in milestone labeled on-testplan, bug, or verification-needed
• Verification steps added to bug and verification-needed issues

Monday morning (Zurich)

@endgame-champ:

• Assign TPIs
  • Create TPI's for all verification needed bugs. Visit Testing and Verification on tools site, and generate groupings, then create TPIs. The TPI section below will update with all of the generated items.
• Pause automatic releases (this also ensures chat-pre-release isn't released) after 10am.
• Run the Start Endgame workflow
  • PRs opened with auto-merge enabled — ensure they get reviewed and merged Monday morning so Insiders picks up the next milestone version:
    • Version bump (microsoft/vscode): Bump version to 1.131.0 #326568
    • Endgame notebook milestone bump (microsoft/vscode): Update endgame notebook milestones to 1.130.0 #326569
  • If you need to run these steps manually, see the Branching guide.
• In absence of the tech writer, follow the steps in the website endgame issue https://github.com/microsoft/vscode-website/issues/2760

Monday morning (Redmond and Zurich)

@team:

• Test plan items. All TPIs must be finished by noon. This includes verification TPIs.
• Make sure your TPIs are being tested and ping folks if to confirm they will finish by noon.

Monday afternoon (Redmond and Zurich)

@team:

• Fix essential issues. Default to pushing to next iteration
• Release notes

Monday EOD Redmond time

@team:

• All issues including late fixes, are verified (query)
• Release notes written

@endgame-champ:

• Create new builds from release/<x.y> branch so we can finish verification.

Tuesday by noon CET

@team:

• Fix essential issues. Default to pushing to next iteration
• Release notes

@endgame-champ:

• Generate "Thank you" section of the release notes in the vnext branch of the vscode-docs repo.
  • Acknowledge third-party pull requests in release notes.
  • Acknowledge issue trackers from the community (do the copy-paste variant) -
• Build and release insiders from release/<x.y>
• Build stable from release/<x.y> and release to MSFT folks
• Reenable automatic releases
  • A build is scheduled for 7:00 PM Zurich time (19:00 GMT+2); make sure automatic releases are reenabled before then so we get an Insiders build from main on Tuesday evening.

Tuesday afternoon/Wednesday morning

• In extreme cases, accept candidate changes
  • Build stable from release/<x.y>. Do not bump the VS Code version.
  • Release stable to MSFT folks

Wednesday

@endgame-champ:

• Publish website so that in-product release notes are ready @rzhao271
• Start Stable rollout to everyone (start percentage: 20%, end time UTC: 6AM next Wednesday)
• Deploy vscode.dev
  • Verify the release candidate release/x.y passed the sanity tests in the last step
  • Kick off deploy (Branch release/x.y, Deployment Target prod, needs peer approval)
• Publish @vscode/chat-lib (Branch release/x.y, Release Version auto, needs peer approval)
• Publish socials (ping Cynthia)
• Publish @types/vscode if you find type diffs after running the steps
• Create an official release
  • 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 version as title <x.y.z> and use the release link https://code.visualstudio.com/updates/v<x_y> for the description
• Close milestone (do not delete it)
• Move all remaining issues to "On Deck"
• Ensure that the latest Insiders release from main has succeeded

[aguilarvillagrandiana29-collab]

Endgame guide

Before Monday 6AM Zurich time

@team:

• Update endgame availability
• Test plan items created
• Milestone only has TPIs. All other issues need to be closed
• All closed issues in milestone labeled on-testplan, bug, or verification-needed
• Verification steps added to bug and verification-needed issues

Monday morning (Zurich)

@endgame-champ:

• • Assign TPIs

    • Create TPI's for all verification needed bugs. Visit Testing and Verification on tools site, and generate groupings, then create TPIs. The TPI section below will update with all of the generated items.[x] Pause automatic releases (this also ensures chat-pre-release isn't released) after 10am.* [x] Run the Start Endgame workflow

    • PRs opened with auto-merge enabled — ensure they get reviewed and merged Monday morning so Insiders picks up the next milestone version:

      • Version bump (microsoft/vscode): Bump version to 1.131.0 #326568* [x] Endgame notebook milestone bump (microsoft/vscode): Update endgame notebook milestones to 1.130.0 #326569* If you need to run these steps manually, see the Branching guide.[x] In absence of the tech writer, follow the steps in the website endgame issue https://github.com/microsoft/vscode-website/issues/2760

Monday morning (Redmond and Zurich)

@team:

• Test plan items. All TPIs must be finished by noon. This includes verification TPIs.
• Make sure your TPIs are being tested and ping folks if to confirm they will finish by noon.

Monday afternoon (Redmond and Zurich)

@team:

• Fix essential issues. Default to pushing to next iteration
• Release notes

Monday EOD Redmond time

@team:

• All issues including late fixes, are verified (query)
• Release notes written

@endgame-champ:

• Create new builds from release/<x.y> branch so we can finish verification.

Tuesday by noon CET

@team:

• Fix essential issues. Default to pushing to next iteration
• Release notes

@endgame-champ:

• • Generate "Thank you" section of the release notes in the vnext branch of the vscode-docs repo.

    • Acknowledge third-party pull requests in release notes.* [x] Acknowledge issue trackers from the community (do the copy-paste variant) -[x] Build and release insiders from release/<x.y>[x] Build stable from release/<x.y> and release to MSFT folks* [x] Reenable automatic releases

    • A build is scheduled for 7:00 PM Zurich time (19:00 GMT+2); make sure automatic releases are reenabled before then so we get an Insiders build from main on Tuesday evening.

Tuesday afternoon/Wednesday morning

• In extreme cases, accept candidate changes

  • Build stable from release/<x.y>. Do not bump the VS Code version.[x] Release stable to MSFT folks

Wednesday

@endgame-champ:

• Publish website so that in-product release notes are ready @rzhao271[x] Start Stable rollout to everyone (start percentage: 20%, end time UTC: 6AM next Wednesday)* [x] Deploy vscode.dev

  • Verify the release candidate release/x.y passed the sanity tests in the last step* [x] Kick off deploy (Branch release/x.y, Deployment Target prod, needs peer approinitionId=683) (Branch release/x.y, Release Version auto, needs peer approval)[x] Publish socials (ping Cynthia)[x] Publish @types/vscode if you find type diffs after running the steps* [x] Create an official release

  • Create a tag (make sure you pull the release branch first): git tag <x.y.z>* [x] Push the tag: git pHub release: [Open the GitHub tags](https://github.com/microsoft/vscode/tags), and click far right ... > Create Release. Use the version as title <x.y.z> and use the release link https://code.visualstudio.com/updates/v<x_y>` for the description[x] Close milestone (do not d