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

March 2021 Endgame #119494

Closed
TylerLeonhardt opened this issue Mar 22, 2021 · 2 comments
Closed

March 2021 Endgame #119494

TylerLeonhardt opened this issue Mar 22, 2021 · 2 comments
Assignees
@jrieken @TylerLeonhardt
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
March 2021

Comments

@TylerLeonhardt
Copy link
Member

TylerLeonhardt commented Mar 22, 2021 •
edited
Loading

  • 3/22 Code freeze for the endgame
  • 3/26 Endgame done
  • 4/03 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
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
    • Windows - owner
    • macOS (Universal) - owner
    • Linux - owner
  • 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. @lszomoru
    • debug-adapter-protocol
    • inno-updater
    • jsonc-parser
    • language-server-protocol
    • 💡localization - @weeteckt
    • 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
    • Trigger new insider build and publish it manually endgame champion
  • Branch code to release/<x.y> endgame champion
  • Bump up the version in package.json on main - endgame champion
  • Announce main is open for business 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
  • Publish website @ornellaalt
  • Publish Localization language pack @weeteckt
  • 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
@TylerLeonhardt TylerLeonhardt added the endgame-plan VS Code - Next release plan for endgame label Mar 22, 2021
@lramos15 lramos15 pinned this issue Mar 22, 2021
@TylerLeonhardt TylerLeonhardt mentioned this issue Mar 22, 2021
Closed
76 tasks
@yubaoquan
Copy link

3/03 Expected release date

not 4/03 ?

@bugpowder
Copy link

That was fast!

@TylerLeonhardt TylerLeonhardt unpinned this issue Apr 1, 2021
@kieferrm kieferrm added this to the March 2021 milestone Apr 10, 2021
@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jrieken jrieken

@TylerLeonhardt TylerLeonhardt

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

No branches or pull requests
5 participants
@bugpowder @jrieken @yubaoquan @TylerLeonhardt @kieferrm