October 2021 Recovery 2 Endgame

[alexr00]

• Create a milestone October 2021 Recovery 2 @alexr00
• Bump the version number @alexr00
• 🔖candidate issues
• Assign candidate issues to the recovery milestone team
• Review the candidate issues, and if they pass the review assign them to the recovery milestone team
• All candidate fixes are peer reviewed and pushed to main and then cherry-picked into the release branch team
• Initiate insiders build from main
• Issues are tested in the insiders team
• Build stable for all platforms from release branch @alexr00
• Issues are verified on stable build and the verified label is added @alexr00
• Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @alexr00
• Update the release notes and include a link to a query for the fixed issues @gregvanl
• Sanity check of installable bits (server instructions)
  • Windows 32 bit @rzhao271
    • signed installer 32-bit
    • signed user installer 32-bit
    • zip 32-bit
    • server 32-bit
  • Windows 64 bit @tanhakabir
    • signed installer 64-bit
    • signed user installer 64-bit
    • zip 64-bit
    • server 64-bit
  • Windows ARM64 @sbatten
    • signed installer ARM64
    • signed user installer ARM64
    • zip ARM64
  • macOS
    • Universal @rzhao271
    • Intel @rzhao271
    • Intel server @rzhao271
    • Apple Silicon @misolori
  • Linux x64
    • deb @lramos15
    • rpm @rzhao271
    • archives @rzhao271
    • snap (sudo snap install --classic --dangerous <file>.snap) @lramos15
  • Linux server @TylerLeonhardt
    • x64
    • x64 Alpine
    • ARM32
    • ARM64
• Publish website @gregvanl
• Publish stable build owner
• Create an official release owner
  • Create a tag: git tag <x.y.z> release/<x.y>
  • 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 correct title and description from our release notes. Example

[lramos15]

1.62.2 released

[JoshStrobl]

@lramos15 The commit for 1.62.2 is the same as the one for 1.62.0, which is b3318bc

[lramos15]

@JoshStrobl Good catch, this was due to me forgetting to pull the new commits before creating the tag 🙃. I've updated the tag to point to the correct commit.