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

September 2023 Endgame #193938

Closed
ghost opened this issue Sep 25, 2023 · 0 comments
Closed

September 2023 Endgame #193938

ghost opened this issue Sep 25, 2023 · 0 comments
Assignees
@chrmarti @bhavyaus
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
September 2023

Comments

@ghost
Copy link

ghost commented Sep 25, 2023 •
edited by bhavyaus
Loading

  • 09/25 Code freeze for the endgame
  • 09/29 Endgame done
  • 10/4 Expected release date (this may change)
Monday
  • Check that all queries in this issue use the current milestone @bhavyaus
  • Run OSS tool @bhavyaus
  • Update links in the Endgame notebooks to point to new milestone @bhavyaus
  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms at 5pm PT
  • 🔖All closed feature-requests either have a verification-needed or on-testplan label
  • Create test plan items following the template here by 6pm PT
    • Remind the team that TPIs should be written so that anyone can test. If this is not feasible, then TPI authors should assign specific testers @bhavyaus
  • Update your availability for testing here - https://tools.code.visualstudio.com/team-manifest team
    • Update availability of testers in vacation (Check OOF section in the Internal Backlog Plan). Double check N/A testers. @bhavyaus
    • Remind team that in the event of sickness or overload with TPIs, to inform the endgame champ ASAP so items can be reassigned
Tuesday
  • Test plan items assigned (using https://tools.code.visualstudio.com/test-plan-items)
    • Run the tool multiple times to balance load if test items come in later and assignments are already made
    • Assigned to you
  • Test build starts at 7am CET
  • Test plan ready by 8am CET
  • Remind the team about the priorities
    • Tuesday should be dedicated exclusively to testing activities. Our goal is to ensure the completion of all Test Plan Items (TPIs) and subsequently proceed with the verification phase. Fixes or commits should be refrained from, unless there are exceptional circumstances such as blocked TPIs or build-related issues
    • Redmond members commence testing the TPIs authored by Zurich members, enabling them to address any feedback on the following day.
  • 🔖Testing
  • 🔖Verification needed
Wednesday
  • 🔖Testing
    • These remaining TPIs should be the ones that are currently blocked. Discuss during the standup and redistrubute assignments based on the TPI owner and the test coverage. For instance, if a TPI is owned by a member from Zurich and has not undergone sufficient testing, it will be reassigned to one of the Zurich team members.
  • Remind team members to triage issues found in testing and assign major issues that they intend to fix to the current milestone
  • 🔖Verification needed
Thursday
  • Make sure to have the insider build @bhavyaus
  • Pause scheduled insider builds (includes vscode.dev publishing) @bhavyaus
  • Fixing (self-assigned, milestone assigned)
    • 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
  • Branch & Release by latest 9AM CET (12AM Thursday PST) @bhavyaus
    • Branch following repositories to release/<x.y>
      • vscode
      • vscode-distro
      • vscode-dev
    • Announce main is open for business
    • Build and manually release Insider from release/<x.y> branch for Code
    • Build and manually release Insider from release/<x.y> branch for vscode.dev (if there were vscode.dev candidates)
  • Build a stable build from release/<x.y> branch to ensure stable build is green @bhavyaus
  • Bump up the version in package.json on main - @bhavyaus
  • Localization: Run Update VS Code Branch build with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) @bhavyaus
  • Create next milestone and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos @bhavyaus
  • Satellite modules/npm packages ready, version updated, smoke tested
  • Only candidate issues are open and assigned to 🔖milestone
  • All issues 🔖verified
  • All open PRs on the milestone 🔖merged or deferred
  • Fixing (PR + review required - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • All release notes updated
    • release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
  • Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the @bhavyaus can generate the pull request acknowledgment for all repositories at once. @bhavyaus
    • 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
  • 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> for Code @bhavyaus
    • Build and manually release Insider from release/<x.y> for vscode.dev (if there were vscode.dev candidates) @bhavyaus
Friday/Monday
  • Polish release notes redmond
  • Fixing (only critical bugs - no string changes)
  • Schedule an endgame restrospective with with @bhavyaus, endgame buddy, and next @bhavyaus for this week. Retrospective template
Monday - Wednesday
  • 🔖milestone issues
  • 🔖candidate issues
  • Polish release notes redmond
  • Cherry-pick hand-picked and reviewed changes to release/<x.y> @bhavyaus
  • Build Insider from release/<x.y> @bhavyaus
  • Manually release Insider @bhavyaus
  • Build stable for all platforms as new candidate issues come in @bhavyaus
  • Documentation updated
  • Run scripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented. @bhavyaus

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

Wednesday/Thursday - Expected release day (this may change)
@ghost ghost added the endgame-plan VS Code - Next release plan for endgame label Sep 25, 2023
@ghost ghost added this to the September 2023 milestone Sep 25, 2023
@ghost ghost assigned bhavyaus and chrmarti Sep 25, 2023
@deepak1556 deepak1556 mentioned this issue Sep 26, 2023
Closed
@bpasero bpasero pinned this issue Sep 26, 2023
@gjsjohnmurray gjsjohnmurray mentioned this issue Sep 26, 2023
Closed
@filiptronicek filiptronicek mentioned this issue Oct 4, 2023
Closed
@bhavyaus bhavyaus closed this as completed Oct 5, 2023
@chrmarti chrmarti unpinned this issue Oct 9, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

@bhavyaus bhavyaus

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
September 2023
Development

No branches or pull requests
3 participants
@chrmarti @bhavyaus and others