Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to support spec v0.6.0 compliance #177

Closed
7 tasks done
toddbaert opened this issue May 16, 2023 · 4 comments
Closed
7 tasks done

Changes to support spec v0.6.0 compliance #177

toddbaert opened this issue May 16, 2023 · 4 comments
Labels

Comments

@toddbaert
Copy link
Member

toddbaert commented May 16, 2023

Implement specification v0.6.0 changes

See changes since last release.

Please note there's no need to complete all these tasks in a single PR (in fact, that's not recommended).

Functional requirements:

Non-functional requirements:

  • add relevant tests
  • add examples and documentation, see template README
  • update specification badge to v0.6.0: Specification

Keep in mind:

  • backwards compatibility is highly encouraged
    • take every precaution to ensure existing code written by application authors and existing providers implementations, do not break
  • it's recommended these features are released together
@toddbaert toddbaert changed the title Changes to support cpec v0.6.0 compliance Changes to support spec v0.6.0 compliance May 16, 2023
@Kavindu-Dodan
Copy link
Contributor

@toddbaert I will start working on the sub task: implement named client support (open-feature/spec@4cf8229)

@Kavindu-Dodan
Copy link
Contributor

I will continue to work on implement initialization/shutdown: open-feature/spec@a4ffec3

@toddbaert
Copy link
Member Author

@Kavindu-Dodan I've created sub-issues and assigned to you. Thanks!

@Kavindu-Dodan
Copy link
Contributor

All functional and non-functional goals have been met with the linked PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants