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

Re-write release test plan document to account for newly automated parts #903

Closed
dbjorge opened this issue Jul 3, 2019 · 1 comment
Closed
Labels
status: resolved This issue has been merged into main and deployed to canary. task

Comments

@dbjorge
Copy link
Contributor

dbjorge commented Jul 3, 2019

As part of this, consider whether to keep using our internal onenote for this, vs using a more public process like VSCode's "endgame-plan" issues (example)

@dbjorge dbjorge added the task label Jul 3, 2019
@dbjorge dbjorge added this to the Feature 1518665 milestone Jul 3, 2019
@msft-github-bot msft-github-bot added the status: new This issue is new and requires triage by DRI. label Jul 3, 2019
@dbjorge
Copy link
Contributor Author

dbjorge commented Aug 5, 2019

Rewrote onenote page accordingly. Did not have time to consider endgame-plan approach.

@dbjorge dbjorge closed this as completed Aug 5, 2019
@msft-github-bot msft-github-bot added status: resolved This issue has been merged into main and deployed to canary. and removed status: new This issue is new and requires triage by DRI. labels Aug 5, 2019
@DaveTryon DaveTryon removed this from the Feature 1518665 milestone Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: resolved This issue has been merged into main and deployed to canary. task
Projects
None yet
Development

No branches or pull requests

3 participants