Give consumers indication of module stability (or likeliness that will be refactored)
Open
topic/project-management
- Dominant language
- Go
- Stars
- 316
- Forks
- 163
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 8
Description
## Done Criteria
There is a clear way for consumer to know which modules are most likely to be changed in a backwards incompatible way.
## Why Important
This helps a consumer know which modules they should be more careful for declaring a dependency on.
## Notes
https://github.com/ipfs/boxo/issues/196 took on bringing in a lot of code to Boxo. This was done in part to allow for easier refactors. We want to make it clear which items are most likely on the "refactor block".
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.