This is the endgame schedule for May 2019 Iteration.
Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
candidate)[ ] All issues verified
[x] Run OSS tool and pass list of changed OSS usage (https://github.com/Microsoft/vscode-build-tools/blob/master/distro-tools/license/third_party_1.nn.0_diff.txt) to @isidorn for verification @rebornix
--stable-build argument ⚠️ )Month_Year.md in this repo directory. ⚠️We are now doing release notes via Git LFS. Please read what this means here: https://github.com/Microsoft/vscode-docs/blob/vnext/README.md#git-lfs-setup⚠️NOT MERGED - PLS REVIEW. @aeschlirelease/<x.y> @rebornixInsider from release/<x.y> @rebornixInsider @rebornixNote: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @rebornix@types/vscode@<x.y> @rebornix insider builds @rebornixCan this be pinned, i.e. so it appears at the top of Issues? maybe the Iteration Plan (#74143) too? That has been done on previous iterations.
Do the iteration plans typically lag VSCode releases? 1.35 is available on the website, but hasn't been updated in the DNF repo (Fedora).
@tristan957 I guess, this line in the plan is somewhat relevant
Publish rpm to repository manually @RMacfarlane
@tristan957 @lig we're still waiting on the signing to be completed, it will probably be published today.
Did the update get published? I see from the checklist that the signing got completed.
We're still waiting on the signing unfortunately, hopefully Monday.
@tristan957 The rpm is now published.
May release is out and closed in favor of https://github.com/microsoft/vscode/issues/75285 .
Most helpful comment
Can this be pinned, i.e. so it appears at the top of Issues? maybe the Iteration Plan (#74143) too? That has been done on previous iterations.