EndGame Schedule
- January 29th Code freeze for the endgame
- February 2nd Endgame done
Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
Monday
Tuesday
Wednesday
Thursday
Friday
Friday/Monday
Monday – Wednesday
Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
Thursday/Friday
Recovery Build
Day 1 (2/13)
Day 2 (2/14)
EndGame Schedule
Monday
Tuesday
Wednesday
Thursday
candidate)Major_Minor.mdin this repo directoryFriday
insiderbuilds Kai Maetzel (@kieferrm)candidate)Friday/Monday
release/<x.y>got created and that translation should be pulled from there and that the pull request has to be created against that branch alexandrudimaMonday – Wednesday
release/<x.y>Ramya Rao (@ramya-rao-a), @ alexandrudimaInsiderfromrelease/<x.y>@Ramya Rao (@ramya-rao-a)InsiderKai Maetzel (@kieferrm)Thursday/Friday
i18nfolder git history for latest translations, then build locally and see the amount of untranslated strings) zurichHEADofrelease/<x.y>in formatx.y.z(for vscode.d.ts download) Ramya Rao (@ramya-rao-a)/alexandrudimainsiderbuilds Daniel Imms (@Tyriar)Recovery Build
Day 1 (2/13)
<Month> Recovery <year>Ramya Rao (@ramya-rao-a)candidateissues, and if they pass the review assign them to the recovery milestone @teamcandiatefixes are peer reviewed and pushed tomasterand then cherry-picked into the release branch @teamstablebuild frommasterstablebuild and theverifiedlabel is added @teamDay 2 (2/14)
https://github.com/Microsoft/vscode/compare/release/<x.y>to ensure no other commits have been made in the release branch Sandeep Somavarapu (@sandy081)HEADofrelease/<x.y>in formatx.y.zJoão Moreno (@joaomoreno)