Spec v0.9.0 compliance
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- backend-api-design
Research direction
Start with the spec v0.9.0 release, the spec submodule, and the gherkin end-to-end harness. Review the linked provider lifecycle requirements and first-party providers, then implement the opt-in provider event ownership and legacy-path deprecation; done means the submodule is at v0.9.0 and the gherkin e2e checks pass.
Written by the indexing model from the issue text.
Description
Tracks spec v0.9.0 compliance. Functionally complete; only harness bump remains.
-
Bump
specsubmodule to the v0.9.0 tag; re-run gherkin e2e. -
Provider lifecycle event ownership (race-condition fix): add opt-in marker so providers emit their own
PROVIDER_READY/PROVIDER_ERROR; SDK derives status from the provider event stream and keeps + deprecates the legacy synthetic path; update first-party providers (spec 5.3.5, provider status 2.8, Appendix E)
- Dominant language
- Java
- Stars
- 128
- Forks
- 61
- Avg merge
- 11h 36m
- Merged PRs (30d)
- 22
Getting set up
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.
More from open-feature/java-sdk
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
open-feature/java-sdk#2019 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-feature/java-sdk#2014 · 1 comment ·
Maintainers usually reply within 1 day
-
on setProvider call, shutting down the previous provider should happen before creating the new oneOpen
Difficulty 3/5 1-2 days Newbie friendliness 50/100
open-feature/java-sdk#1934 · 1 reaction ·
Maintainers usually reply within 1 day
-
multi-provider
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-feature/java-sdk#1882 ·
Maintainers usually reply within 1 day
-
[Multi-provider] Reconsider type of "originalMetadata"May be free again @chrfwow claimed this 229 days ago, and no pull request is open. Open
open-feature/java-sdk#1792 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in open-feature/java-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
checkstyle/checkstyle#21755 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/copilot-sdk#2782 ·
Maintainers usually reply within 1 day
-
documentation Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#519 ·
Maintainers usually reply within 1 day
-
area-deployment triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/aspire#20533 · 1 comment ·
Maintainers usually reply within 1 day