Closed
Description
Endgame: microsoft/vscode#148074
Expected release date: 05/04
DRI: @filiptronicek @jeanp413
Plan:
- Create corresponding release branches for
main
andgp-code/main
- Create release branch
release/1.67
- Execute the rebase from upstream:
./scripts/sync-with-upstream.sh upstream/release/1.67 release/1.67
- Execute the rebase from upstream:
- Create release branch
gp-code/release/1.67
- Execute the rebase from upstream:
./scripts/sync-with-upstream.sh upstream/release/1.67 gp-code/release/1.67
- Execute the rebase from upstream:
- Create release branch
- Switch nightly jobs in https://github.com/gitpod-io/openvscode-releases and Gitpod Code-Nightly GitHub actions to point to the release branches
- Create and merge PR in Gitpod repo to generate stable image for VS Code [code]: Generate stable images for 1.67 #9761
- Use the template from https://gist.github.com/filiptronicek/be19dcab639a1cdf08089cc762377a41
- Smoke test version 1.67 in VS Code Insiders
- Create and merge PR in Gitpod repo updating VS Code stable image tags to image generated in previous step [code] Update stable to 1.67 #9777
- Deploy VS Code Insiders as stable
- Release OpenVSCode Server https://github.com/gitpod-io/openvscode-server/releases/tag/openvscode-server-v1.67.0
- Port fixes from release/1.67 to main if any
- Switch nightly jobs in https://github.com/gitpod-io/openvscode-releases and Gitpod Code-Nightly GitHub actions to point back to
main
andgp-code/main
branch - Monitor for recovery releases and provide corresponding release in Gitpod and OpenVSCode if necessary
Metadata
Metadata
Assignees
Type
Projects
Status
Done