Update bug-report.yaml for 1.6-exp1

[duncanmacmichael]

A microsoft employee must use /azp run to validate using the pipelines below.

WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran.

For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

[Gaoyifei1011]

A microsoft employee must use /azp run to validate using the pipelines below.

WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran.

For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release?

我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

[christosk92]

A microsoft employee must use /azp run to validate using the pipelines below. WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran. For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release?

我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

Please keep in mind that Redmond is on GMT-7. Which means there is a 15 hour time difference between Beijing and Microsoft. This PR was made on Friday, then it's weekend which are non office hours. They just finished their first day of the week. I'm sure they'll release it soon :)

[Gaoyifei1011]

A microsoft employee must use /azp run to validate using the pipelines below. WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran. For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release? 我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

Please keep in mind that Redmond is on GMT-7. Which means there is a 15 hour time difference between Beijing and Microsoft. This PR was made on Friday, then it's weekend which are non office hours. They just finished their first day of the week. I'm sure they'll release it soon :)

Thank you very much for your answer. Hope to see the new version released soon.

[codendone]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).