-
Notifications
You must be signed in to change notification settings - Fork 677
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
Update Bug Report template #6673
Conversation
Added Windows 19044 build to the Bug report template
Improved OS version and build readability
@gabbybilka thoughts? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
- "Fall Creators Update (16299)" | ||
- "Creators Update (15063)" | ||
- "Windows Insider Build (xxxxx)" | ||
- "Windows 11: Build 22000" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be helpful to use the code names as well for the Windows 10 builds as they are relatively well known: https://en.wikipedia.org/wiki/Windows_10_version_history#Channels
I propose this format:
Windows 10: Build 19044 --> Windows 10 21H2: Build 19044
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like version — good call!
Windows 11 (21H2): Build 22000
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the template with the last commit
Now all the Windows versions have the same style: `Windows [version] (version abbreviation): Build xxxxx` Example: Windows 11 (21H2): Build 22000
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks for contributing! 🙂
Thank you for such cool technology) @StephenLPeters, I suppose, that it's needed to run Azure pipelines again, to finish the PR? |
Commenter does not have sufficient privileges for PR 6673 in repo microsoft/microsoft-ui-xaml |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
How can I sign the CLA? |
Description
Windows 11: Build 22000
Windows 10: Build 19044
Motivation and Context
First - absence of the latest OS build is pretty confusing.
Also, I think, that restructuring of the OS version chapter will improve contributor's readability.
Screenshot: