open-feature / open-feature/flagd
[DOCS] Define rules for semantic versioning
Open
@cupofcat is already working on this.
Since Sep 1, 2025.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
- define API stability guarantees and breaking-change review checklist
- define a “breaking change”
- create deprecation policy
- create requirements for authoring migration-guide
- set per-minor release cadence
- define active-support windows
- create policy for back-porting severe-bug and security fixes
- publish conformance reports with each minor release
- include benchmark report with each minor release [Depends on benchmarking automation]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.