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.

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

November 2021 Endgame #137919

Closed
deepak1556 opened this issue Nov 26, 2021 · 0 comments
Closed

November 2021 Endgame #137919

deepak1556 opened this issue Nov 26, 2021 · 0 comments
Assignees
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone

Comments

@deepak1556
Copy link
Collaborator

deepak1556 commented Nov 26, 2021

  • November 29, 2021 Code freeze for the endgame
  • December 03, 2021 Endgame done
  • December 09, 2021 Expected release date (this may change)
Monday
  • Check that all queries in this issue use the current milestone endgame champion
  • Run OSS tool endgame champion
  • Update links in Endgame issue and Endgame notebooks to point to new milestone endgame champion
  • Code freeze at 5pm PT (10am JST)
  • Ensure we have a green build on all platforms at 5pm PT (10am JST)
  • Create test plan items following the template here by 6pm PT (11am JST)
  • Add verification-needed label to features needed testing and are not tested by TPIs.
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/testers team
    • Update availability of testers in vacation. Double check N/A testers. endgame champion
Tuesday
Wednesday
Thursday
  • 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
  • All issues 🔖verified
  • Branch code to release/1.63 after all expected fixes are in (latest 5PM PST/ 10am JST) endgame champion
  • Branch distro to release/1.63 after all expected fixes are in (latest 5PM PST/ 10am JST) 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/1.63 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
Friday/Monday
  • Polish release notes redmond
  • Fixing (only critical bugs - no string changes)
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. endgame champion

Wednesday/Thursday - Expected release day (this may change)
  • Build stable for all platforms endgame champion
  • Sanity check of installable bits (server instructions)
    • Windows 32 bit @dbaeumer
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
      • server 32-bit
    • Windows 64 bit @alexr00
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
      • server 64-bit
    • Windows ARM64 @deepak1556
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS @sandy081
      • Universal
      • Intel
      • Intel server
      • Apple Silicon
    • Linux x64 @aeschli
      • deb
      • rpm
      • archives
      • snap (sudo snap install --classic --dangerous <file>.snap)
    • Linux server @chrmarti
      • x64
      • x64 Alpine
      • ARM32
      • ARM64
  • Publish website @gregvanl
  • Publish to stable endgame champion
  • Create an official release endgame champion
    • Create a tag: 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
@deepak1556 deepak1556 added the endgame-plan VS Code - Next release plan for endgame label Nov 26, 2021
@deepak1556 deepak1556 added this to the November 2021 milestone Nov 26, 2021
@deepak1556 deepak1556 pinned this issue Nov 26, 2021
@chrmarti chrmarti assigned chrmarti and unassigned alexr00 Nov 26, 2021
@deepak1556 deepak1556 unpinned this issue Dec 10, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Development

No branches or pull requests

4 participants