Make extension release docs as comprehensive as azd release docs
Open
area/extensions
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
We should make sure the extension release process documents are as self-contained as possible. They lack some of the things in the main azd release process docs like how to decide between path and minor version bumps. It's also worth looking at how much of these we can extend to our skills (i.e., choosing the next version automatically).
Contributor guide
Assessment
This issue has not been assessed yet.