Closed
Description
Bug description
Endgame: microsoft/vscode#161755
Expected release date: 10/05
DRI: @jeanp413 @filiptronicek
Plan:
- Create corresponding release branches for
main
andgp-code/main
- Create release branch
release/1.72
- Execute the rebase from upstream:
./scripts/sync-with-upstream.sh upstream/release/1.72 release/1.72
- Execute the rebase from upstream:
- Create release branch
gp-code/release/1.72
- Execute the rebase from upstream:
./scripts/sync-with-upstream.sh upstream/release/1.72 gp-code/release/1.72
- Turn off all
experimental
feature flags in gitpod-web- Ports view (akin to gitpod-io/openvscode-server@488fe48)
- 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 (Build stable image for VS Code Browser 1.72 #13617)
- Use the template from https://gist.github.com/filiptronicek/be19dcab639a1cdf08089cc762377a41
- Smoke test version 1.72 in VS Code Insiders
- Create and merge PR in Gitpod repo updating VS Code stable image tags to image generated in previous step
- Deploy VS Code Insiders as stable
- Release OpenVSCode Server
- Port fixes from
release/1.72
tomain
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