The Wayback Machine - https://web.archive.org/web/20221219144509/https://github.com/Microsoft/vscode/issues/69177
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

Jump to bottom

February 2019 Endgame #69177

Closed
135 tasks done
octref opened this issue Feb 21, 2019 · 2 comments
Closed
135 tasks done

February 2019 Endgame #69177

octref opened this issue Feb 21, 2019 · 2 comments
Assignees
@octref
Labels
endgame-plan VS Code - Next release plan for endgame

Comments

@octref
Copy link
Contributor

octref commented Feb 21, 2019 •
edited

This is the endgame schedule for February 2019 Iteration.

Schedule

  • End game master: @octref / Redmond
  • End game buddy: @dbaeumer / Zurich
  • 02/22 Code freeze for the endgame
  • 03/01 Endgame done
  • 03/07 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.

Friday 02/22
  • Run OSS tool @octref
    • 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 sufficiently comprehensive test descriptions by 6pm PT
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/
Monday 02/25
  • 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
Tuesday 02/26
  • Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification
Wednesday 02/27
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Verification
  • Check new OSS usage is entered into the OSS registry owner
Thursday/Friday 02/28 – 03/01
Friday/Monday
  • Branch code to `release/<x.y> @octref
  • Bump up the version in package.json - @octref
  • Announce master is open for business @octref
  • 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
@octref octref added the endgame-plan VS Code - Next release plan for endgame label Feb 21, 2019
@kieferrm kieferrm mentioned this issue Feb 21, 2019
Closed
35 tasks
@connorshea
Copy link
Contributor

connorshea commented Feb 22, 2019

Should this issue be pinned like #68293?

@octref octref pinned this issue Feb 24, 2019
@KexyBiscuit KexyBiscuit mentioned this issue Mar 1, 2019
Closed
@WorldofBay WorldofBay mentioned this issue Mar 7, 2019
Closed
@octref
Copy link
Contributor Author

octref commented Mar 7, 2019

Shipped.

@octref octref closed this as completed Mar 7, 2019
@mjbvz mjbvz unpinned this issue Mar 7, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@octref octref

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@connorshea @octref