open-feature / open-feature/flagd
flagd 1.0 Release
Open
Nobody has claimed this yet.
v1.0-prereq
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
flagd 1.0 release
Goals
- identify and implement remaining features required for 1.0, particularly those that might involve breaking changes
- identify, deprecate, and remove legacy features and options
- stabilize protocols, schemas, and spec
- 1.0 of https://flagd.dev/schema/v0/flags.json with any breaking changes implemented
- update documentation
- update README
- reposition/refine scope of flagd (framework not just daemon)
- complete e2e test coverage
- gherkin reporting?
- providers updated where relevant
Non-Goals
- implement every possible extension/feature (for example, a hypothetical redis sync could be added post 1.0)
- user interface
Tasks
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.
Research direction
Start by reviewing the 1.0 goals and current flagd scope, then inspect the v0 flags schema, README, end-to-end tests, and provider implementations. Done means the remaining 1.0 requirements, breaking changes, legacy options, protocols, schemas, documentation, test coverage, and relevant provider updates are completed and the release scope is settled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100