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

June 2021 Endgame #127394

Closed
chrmarti opened this issue Jun 29, 2021 · 0 comments
Closed

June 2021 Endgame #127394

chrmarti opened this issue Jun 29, 2021 · 0 comments
Assignees
@chrmarti
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
June 2021

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Jun 29, 2021 •
edited by weinand
Loading

  • June 29 Code freeze for the endgame
  • July 2 Endgame done
  • July 7 Expected release date (this may change)
Monday
Tuesday
Wednesday
  • 🔖Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • 🔖Verification needed
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame champion
Thursday
  • Fixing (self-assigned, milestone assigned, NO discussion during standup)
    • Move issues to the next month that can be deferred
  • 🔖Verification needed
  • 🔖Verification
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame champion
Friday
  • Pause scheduled insider builds endgame champion
  • Satellite modules/npm packages ready, version updated, smoke tested
  • All issues 🔖verified
  • Branch code to release/<x.y> endgame champion
  • Fixing (scrutiny sets in once branched - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
  • 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-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
  • Bump up the version in package.json on main - endgame champion
  • Announce main is open for business 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

Tuesday/Wednesday (the day before the release)
Wednesday/Thursday - Expected release day (this may change)
  • Build stable for all platforms endgame champion
  • Sanity check of installable bits
    • 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 @joaomoreno
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS @jrieken
      • Universal
      • Intel
      • Intel server
      • Apple Silicon
    • Linux x64 @aeschli
      • deb
      • rpm
      • archives
      • snap (sudo snap install --classic --dangerous <file>.snap)
    • Linux server @aeschli
      • x64
      • x64 Alpine
      • ARM32
      • ARM64
    • Server instructions
  • Publish website @gregvanl
  • Publish Localization language pack @TylerLeonhardt 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
  • 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. Example
  • Publish @types/vscode endgame champion
  • Enable scheduled insider builds endgame champion
  • Twitter announcement @chrisdias
@chrmarti chrmarti added the endgame-plan VS Code - Next release plan for endgame label Jun 29, 2021
@chrmarti chrmarti added this to the June 2021 milestone Jun 29, 2021
@chrmarti chrmarti self-assigned this Jun 29, 2021
@egamma egamma pinned this issue Jun 29, 2021
@brettfo brettfo mentioned this issue Jun 30, 2021
Closed
@sean-mcmanus sean-mcmanus mentioned this issue Jul 8, 2021
Closed
@bpasero bpasero unpinned this issue Jul 9, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Aug 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
June 2021
Development

No branches or pull requests
2 participants
@chrmarti @meganrogge