EngSys Resiliency
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Following the branch deletion post-mortem and other discussions, we've identified a number of improvements we can make to the Azure SDK engineering system to increase resiliency. Here are issues tracking what we've identified so far:
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3473
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3472
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3474
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3475
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3476
- [ ] https://github.com/Azure/azure-sdk-tools/issues/3477
Contributor guide
Research direction
Start by reviewing the linked tracking issues 3473 through 3477, including the nested issue 3472, and the branch deletion post-mortem referenced in this issue. Determine the intended resiliency work from those issue descriptions; done means the identified engineering-system improvements are addressed and their tracking issues are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100