Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

February 2022 Endgame #143606

Closed
hediet opened this issue Feb 22, 2022 · 1 comment
Closed

February 2022 Endgame #143606

hediet opened this issue Feb 22, 2022 · 1 comment
Assignees
@Tyriar @hediet
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
February 2022

Comments

@hediet
Copy link
Member

hediet commented Feb 22, 2022 •
edited by Tyriar
Loading

  • 02/23 Code freeze for the endgame
  • 02/28 Endgame done
  • 03/03 Expected release date (this may change)
Tuesday
Wednesday
Thursday
Friday
  • Fixing (self-assigned, milestone assigned, no need for PR or review)
    • Increased scrutiny sets in due to testing being completed. Fixes pose a much higher risk
    • Move issues to the next month that can be deferred
  • 🔖Verification needed
  • 🔖Verification
Friday
  • Build a stable build to ensure stable build is green endgame champion
  • Pause scheduled insider builds endgame champion
  • Satellite modules/npm packages ready, version updated, smoke tested
  • Only candidate issues are open and assigned to 🔖milestone
  • All issues 🔖verified
  • Branch code to release/<x.y> after all expected fixes are in (latest 5PM PST) endgame champion
  • Branch distro to release/<x.y> after all expected fixes are in (latest 5PM PST) endgame champion
  • Announce main is open for business endgame champion
  • Fixing (PR + review required once branched - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • All release notes updated
  • Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the endgame champion can generate the pull request acknowledgment for all repositories at once. endgame champion
    • debug-adapter-protocol, inno-updater, jsonc-parser, language-server-protocol, lsif-node, vscode, vscode-codicons, vscode-css-languageservice, vscode-debugadapter-node, vscode-dev-containers, vscode-docs, vscode-emmet-helper, vscode-eslint, vscode-extension-samples, vscode-generator-code, vscode-hexeditor, vscode-html-languageservice, vscode-js-debug, vscode-js-debug-companion, vscode-js-profile-visualizer, vscode-jshint, vscode-json-languageservice, vscode-languageserver-node, vscode-livepreview, vscode-loader, vscode-lsif-extension, vscode-node-debug, vscode-node-debug2, vscode-pull-request-github, vscode-recipes, vscode-references-view, vscode-textmate, vscode-vsce
  • Acknowledge issue trackers from the community @chrmarti
  • Add notable fixes to the release notes all
  • When done fixing/verifying and there are changes since last build at the end of day PT
    • Build and manually release Insider from release/<x.y> endgame champion
  • Localization: Run Update VS Code Branch in the vscode-loc-drop repo with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) endgame champion
Monday/Tuesday
  • Polish release notes redmond
  • Fixing (only critical bugs - no string changes)
Wednesday - Thursday

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame. endgame champion

Thursday - Expected release day (this may change, higher chance of delay due to endgame starting a day late)
  • Build stable for all platforms endgame champion
  • Sanity check of installable bits (server instructions)
    • Windows 32 bit owner
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
      • server 32-bit
    • Windows 64 bit owner
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
      • server 64-bit
    • Windows ARM64 owner
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS
      • Universal owner
      • Intel owner
      • Intel server owner
      • Apple Silicon owner
    • Linux x64
      • deb owner
      • rpm owner
      • archives owner
      • snap (sudo snap install --classic --dangerous <file>.snap) owner
    • Linux server owner
      • x64
      • x64 Alpine
      • ARM32
      • ARM64
  • Publish website @gregvanl
  • Publish to stable endgame champion
  • Create an official release endgame champion
    • Create a tag (make sure you pull the release branch first): git tag <x.y.z>
    • 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. Also change the relative links for the key highlight list items to absolute links Example
  • Twitter announcement @chrisdias
  • Enable scheduled insider builds endgame champion
  • Bump up the version in package.json on main - endgame champion
  • Publish @types/vscode endgame champion
@hediet hediet added the endgame-plan VS Code - Next release plan for endgame label Feb 22, 2022
@hediet hediet added this to the February 2022 milestone Feb 22, 2022
@hediet hediet pinned this issue Feb 22, 2022
@alexr00 alexr00 mentioned this issue Feb 22, 2022
Closed
@Tyriar
Copy link
Member

Tyriar commented Mar 3, 2022

1.65 has been released

@Tyriar Tyriar closed this as completed Mar 3, 2022
@mustard-mh mustard-mh mentioned this issue Mar 4, 2022
Merged
@kieferrm kieferrm unpinned this issue Mar 6, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

@hediet hediet

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
February 2022
Development

No branches or pull requests
2 participants
@Tyriar @hediet