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

Endgame - misses smoke test before closing for release #91592

Closed
bpasero opened this issue Feb 26, 2020 · 5 comments
Closed

Endgame - misses smoke test before closing for release #91592

bpasero opened this issue Feb 26, 2020 · 5 comments
Assignees
Labels
important Issue identified as high-priority
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Feb 26, 2020

Looking either at https://github.com/microsoft/vscode/wiki/Endgame-Template or #91278 I only see the smoke test mentioned once in the beginning of the week. However I think we need to run them also at the end before closing for the release.

Please update the template and the endgame plan accordingly.

@bpasero bpasero added the important Issue identified as high-priority label Feb 26, 2020
@bpasero bpasero added this to the February 2020 milestone Feb 26, 2020
@Tyriar
Copy link
Member

Tyriar commented Feb 26, 2020

@bpasero isn't that the point of running them early? @jrieken reached out to me asking for the opposite.

@bpasero
Copy link
Member Author

bpasero commented Feb 26, 2020

@Tyriar my understanding was that we run them early to be able to fix issues early on and not on the last day. I was never thinking we would then not run them again before we close for the release. After all, that is actually the purpose of the smoke test - e.g. to verify that there is no data or UI state loss.

Running them once while we still make changes defeats the purpose imho.

@jrieken
Copy link
Member

jrieken commented Feb 26, 2020

Running them once while we still make changes defeats the purpose imho.

Which isn't Friday but usually Monday, Tuesday, sometimes Wednesday.

@bpasero
Copy link
Member Author

bpasero commented Feb 26, 2020

Yeah, then let's run them as part of the sanity checking of builds. In fact, that would probably be the replacement for the rather stupid sanity checking we do today.

@Tyriar
Copy link
Member

Tyriar commented Feb 27, 2020

Ok, I'll add it back where they were (Friday). Can have a discussion with the team if you want to move it to the following week.

@Tyriar Tyriar closed this as completed Feb 27, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
important Issue identified as high-priority
Projects
None yet
Development

No branches or pull requests

3 participants