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.

Sign up for GitHub

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

Jump to bottom

[Breaking Change][Documentation] Consolidate "breaking changes" workflow guidance #5983

Closed
5 tasks
konrad-jamrozik opened this issue Apr 14, 2023 · 1 comment
Closed
5 tasks

[Breaking Change][Documentation] Consolidate "breaking changes" workflow guidance #5983

konrad-jamrozik opened this issue Apr 14, 2023 · 1 comment
Assignees
@konrad-jamrozik
Labels
Breaking Changes Improvements to Breaking Changes tooling Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo.

Comments

@konrad-jamrozik
Copy link
Contributor

konrad-jamrozik commented Apr 14, 2023 •
edited
Loading

Tasks:

  • Write down document explaining how the entire "breaking change" workflow works
    • Explain all the Unified Pipeline checks: what do they check, where is their source, common dev tasks
    • Extract the relevant part from the labelling diagram
    • Explain different subtypes of breaking changes: ARM, data plane or SDKs.
    • Link to relevant docs, e.g. the policy doc, or the ARM RP meeting prep doc (get this info from this doc)

Related work

Reference
@konrad-jamrozik konrad-jamrozik added Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo. labels Apr 14, 2023
@konrad-jamrozik konrad-jamrozik self-assigned this Apr 14, 2023
@konrad-jamrozik konrad-jamrozik mentioned this issue Apr 14, 2023
Closed
@konrad-jamrozik konrad-jamrozik changed the title Consolidate "breaking change" workflow guidance Consolidate "breaking changes" workflow guidance Apr 14, 2023
@konrad-jamrozik konrad-jamrozik moved this from 🤔 Triage to 🐝 Dev in Azure SDK EngSys 🚢🎉 Apr 17, 2023
@konrad-jamrozik konrad-jamrozik added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 18, 2023
@konrad-jamrozik konrad-jamrozik moved this to 📋 Backlog in Spec PR Tools Apr 18, 2023
@konrad-jamrozik konrad-jamrozik removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 18, 2023
@konrad-jamrozik konrad-jamrozik changed the title Consolidate "breaking changes" workflow guidance [Breaking Change] Consolidate "breaking changes" workflow guidance May 12, 2023
@konrad-jamrozik konrad-jamrozik moved this from 🐝 Dev to 📋 Backlog in Azure SDK EngSys 🚢🎉 May 16, 2023
@mikekistler mikekistler added the Breaking Changes Improvements to Breaking Changes tooling label Jun 19, 2023
@konrad-jamrozik konrad-jamrozik changed the title [Breaking Change] Consolidate "breaking changes" workflow guidance [Breaking Change][Documentation] Consolidate "breaking changes" workflow guidance Sep 1, 2023
@konrad-jamrozik
Copy link
Contributor Author

konrad-jamrozik commented Mar 27, 2024 •
edited
Loading

Closing. Some parts of this have been achieved in:

Which was done as part of:

@github-project-automation github-project-automation bot moved this from 📋 Backlog to 🎊 Closed in Spec PR Tools Mar 27, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to 🎊 Closed in Azure SDK EngSys 🚢🎉 Mar 27, 2024
@konrad-jamrozik konrad-jamrozik mentioned this issue Mar 27, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@konrad-jamrozik konrad-jamrozik

Labels
Breaking Changes Improvements to Breaking Changes tooling Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo.
Projects
Azure SDK EngSys 🚢🎉
Archived in project
Spec PR Tools
Status: 🎊 Closed
Milestone
No milestone
Development

No branches or pull requests
2 participants
@konrad-jamrozik @mikekistler