Chris Stackhouse
Chris Stackhouse
@MattGertz, @konrad-jamrozik - Note: I changed the doc link suggested by Konrad to point to its parent, since that seemed to be a little bit better landing page. Either one...
> Update: the email thread is ongoing and we are working on article to be hyperlinked from the PR template, which is [aka.ms/typespec/conversion](https://aka.ms/typespec/conversion). Updated the link.
> Please refer to this guideline https://github.com/Azure/azure-cli/tree/dev/doc/authoring_command_modules#format-pr-title and specify the breaking changes included in this PR in the `History Notes` section.  Updated
> Additionally, since you missed the Build Breaking Change Window, we can only postpone it to the Ignite Breaking Change Window to release it OK. What's the process for that?
> > OK. What's the process for that? > > This is the process https://github.com/Azure/azure-cli/blob/dev/doc/how_to_introduce_breaking_changes.md about how to introduce Breaking Changes @zhoxing-ms - I believe we've done everything documented there....
> @mentat9 Actually, what I want to ask is, could you specify which breaking changes are there? Because customers need to know the details of these breaking changes to help...
@kairu-ms - Can you run the automation again? I don't understand why it's waiting and why I can't run it myself.
> May I ask if this PR is just a migration of CodeGen? Or are there any changes that customers can perceive (such as the release of new features or...
This issue doesn't repro on current versions of VSCode, and required extensions: VSCode: 1.92.1 .NET Install Tool: 2.1.1 Azure Resources: 0.9.1 Azure Account: 0.12.0 Azure Resource Manager (ARM) Tools: 0.15.12...