January 2025 Recovery 2

[connor4312]

• Create a milestone January 2025 Recovery 2 @connor4312
• Bump the version number @connor4312
• 🔖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 and manually release Insider from main branch for vscode.dev (if there were vscode.dev candidates)
  • Issues are tested in the insiders team
• Build stable for all platforms from release branch @connor4312
• Issues are verified on stable build and the verified label is added @connor4312
• Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @connor4312
• 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 @bpasero
    • System Installer
    • User Installer
    • Archive
    • Server @TylerLeonhardt
    • CLI
  • macOS Intel @isidorn
    • Archive
    • Universal Archive
    • Server
    • CLI
  • macOS ARM64 @jrieken
    • Archive
    • Universal Archive
    • Server
    • CLI
  • Linux x64 @deepak1556
    • Archive
    • DEB
    • RPM
    • Snap
  • Linux Server (can be tested from any OS with Docker) @ulugbekna
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
  • Linux CLI (can be tested from any OS with Docker) @hediet
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
• Publish website @connor4312
• Publish stable build @connor4312
• (if there were vscode.dev candidates) Trigger the vscode.dev Deploy pipeline for release/x.y for the prod deployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions @connor4312
  • Request approval from another team member at the necessary step to deploy the vscode.dev build. @connor4312
• Create an official release @connor4312
  • 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 @connor4312

[albertosantini]

Just update to 1.97.1, but I don't see any issue January 2025 Recovery 1.

Ok I see a milestone January 2025 Recovery 1
https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+milestone%3A%22January+2025+Recovery+1%22+

Thanks for your efforts.