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

April 2019 Endgame #73175

Closed
aeschli opened this issue May 2, 2019 · 1 comment
Closed

April 2019 Endgame #73175

aeschli opened this issue May 2, 2019 · 1 comment
Assignees
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone

Comments

@aeschli
Copy link
Contributor

aeschli commented May 2, 2019

This is the endgame schedule for April 2019 Iteration.

Schedule

  • End game master: @aeschli / Zurich
  • End game buddy: @RMacfarlane / Redmond
  • 05/06 Code freeze for the endgame
  • 05/10 Endgame done
  • 05/17 Expected release date (this may change)

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

Monday 05/06
  • Run OSS tool @aeschli
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms at 5pm PT
  • All test items contain test meta data by 5pm PT and sufficiently comprehensive test descriptions by 8am CET
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/
Tuesday
  • Test plan items assigned (using https://vscode-tools.azurewebsites.net/)
    • Run the tool multiple times to balance load if test items come in later and assignments are already made
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Test build starts at 7am CET
  • Test plan ready by 8am CET
  • Testing
  • Verification needed
Wednesday
  • Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification
Thursday
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Verification
Friday
Friday/Monday
  • Branch code to `release/<x.y> @aeschli
  • Bump up the version in package.json - @aeschli
  • Announce master is open for business @aeschli
  • Polish release notes redmond
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.

Wednesday/Thursday
  • Build stable for all platforms @aeschli
  • Make rpm signing request @RMacfarlane
  • Sanity check of installable bits
    • Windows
      • signed installer 32-bit
      • signed installer 64-bit
      • signed user installer 32-bit
      • signed user installer 64-bit
      • zip 32-bit
      • zip 64-bit
    • OS X
    • Linux
      • deb package 32-bit
      • deb package 64-bit
      • rpm package 64-bit
      • rpm package 32-bit
      • archive 32-bit
      • archive 64-bit
  • Publish website @gregvanl
  • Publish Localization language pack @shawndon
  • Publish to stable @aeschli
  • Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @aeschli
  • Publish @types/vscode@<x.y> @octref
  • Publish rpm to repository manually @RMacfarlane
  • Enable scheduled insider builds @aeschli
  • Twitter announcement @auchenberg
@aeschli aeschli self-assigned this May 2, 2019
@aeschli aeschli added the endgame-plan VS Code - Next release plan for endgame label May 2, 2019
@aeschli aeschli added this to the April 2019 milestone May 2, 2019
@aeschli aeschli pinned this issue May 2, 2019
@parzh
Copy link

parzh commented May 4, 2019

@kieferrm kieferrm unpinned this issue May 20, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 4, 2019
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

2 participants