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

January 2022 Endgame #141298

Closed
hediet opened this issue Jan 24, 2022 · 4 comments
Closed

January 2022 Endgame #141298

hediet opened this issue Jan 24, 2022 · 4 comments
Assignees
@deepak1556 @hediet @lramos15
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
January 2022

Comments

@hediet
Copy link
Member

hediet commented Jan 24, 2022 •
edited by lramos15
Loading

  • January 24, 2022 Code freeze for the endgame
  • January 28, 2022 Endgame done
  • February 03, 2022 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
  • Ensure we have a green build on all platforms at 5pm PT
  • Create test plan items following the template here by 6pm PT
  • 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/team 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
  • 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
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 owner @isidorn
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
      • server 32-bit
    • Windows 64 bit owner @isidorn
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
      • server 64-bit
    • Windows ARM64 owner @deepak1556
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS @jrieken
      • Universal owner
      • Intel owner
      • Intel server owner
      • Apple Silicon owner
    • Linux x64 @aeschli
      • deb owner
      • rpm owner
      • archives owner
      • snap (sudo snap install --classic --dangerous <file>.snap) owner
    • Linux server owner @chrmarti
      • 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 pinned this issue Jan 24, 2022
@eamodio
Copy link
Contributor

eamodio commented Jan 24, 2022

@hediet 👋 I seem to still be assigned items on this 😂

@deepak1556 deepak1556 added this to the January 2022 milestone Jan 24, 2022
@deepak1556 deepak1556 added the endgame-plan VS Code - Next release plan for endgame label Jan 24, 2022
@deepak1556
Copy link
Contributor

👋 @eamodio , fixed the assignments :)

@TylerLeonhardt
Copy link
Member

@eamodio you sure you don't want any TPIs?

@eamodio
Copy link
Contributor

eamodio commented Jan 24, 2022

I'd be open to grabbing a couple for commit rights again 😂

@jeanp413 jeanp413 mentioned this issue Feb 3, 2022
Merged
@hediet hediet closed this as completed Feb 4, 2022
@jrieken jrieken unpinned this issue Feb 5, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@deepak1556 deepak1556

@hediet hediet

@lramos15 lramos15

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

No branches or pull requests
5 participants
@eamodio @deepak1556 @TylerLeonhardt @hediet @lramos15