[Release Planner]: Need doc on how people could update the release planner on the wrong input.
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
There are certain cases that people have the wrong input for the release planner.
Some of them could be recovered easily by updating some fields directly while other may requires create a new release planner. (e.g. use a new API version, switch the release for GA/Preview)
Today, we don't have document to describe what actions service team could take to recover from the wrong input. So it would be helpful if release planner could have doc on this.
bot answer: https://teams.microsoft.com/l/message/19:603d15bc0fd248ff82a8326da7322a4d@thread.tacv2/1755766287215?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
original post: https://teams.microsoft.com/l/message/19:de3fce22c2994be18cac50502c55f717@thread.skype/1744129542941?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
https://github.com/Azure/azure-sdk-pr/issues/2364
Contributor guide
Assessment
This issue has not been assessed yet.