April 2024 Recovery 1

[lramos15]

• Create a milestone April 2024 Recovery 1 @lramos15
• Bump the version number @lramos15
• 🔖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 @lramos15 (@Yoyokrazy)
• Issues are verified on stable build and the verified label is added @lramos15 (@Yoyokrazy)
• Check https://github.com/Microsoft/vscode/compare/release/1.89.0 to ensure no other commits have been made in the release branch @lramos15 (@Yoyokrazy)
• The insiders build with all candidate fixes needs to be in the wild for 24 hours before recovery release, unless explicitly approved by @kieferrm
• Update the release notes and include a link to a query for the fixed issues @ntrogh
• Sanity Testing
  • Windows 64 bit @dbaeumer
    • System Installer
    • User Installer
    • Archive
    • Server
    • CLI
  • Windows ARM64 @joaomoreno
    • System Installer
    • User Installer
    • Archive
    • CLI
  • macOS Intel @deepak1556
    • Archive
    • Universal Archive
    • Server
    • CLI
  • macOS ARM64 @sandy081
    • Archive
    • Universal Archive
    • Server
    • CLI
  • Linux x64 @aeschli
    • Archive
    • DEB
    • RPM
    • Snap
  • Linux Server @chrmarti (can be tested from any OS with Docker)
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
  • Linux CLI @alexr00 (can be tested from any OS with Docker)
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
• Publish website @lramos15 (@Yoyokrazy)
• Publish stable build @lramos15 (@Yoyokrazy)
• Create an official release @lramos15 (@Yoyokrazy)
  • Create a tag (make sure you pull the release branch first): 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
• Close the milestone on GitHub @lramos15 (@Yoyokrazy)