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.

Sign up for GitHub

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

Jump to bottom

Proposed timeline for spec and SDK stability #146

Closed
toddbaert opened this issue Sep 29, 2022 · 1 comment
Closed

Proposed timeline for spec and SDK stability #146

toddbaert opened this issue Sep 29, 2022 · 1 comment
Assignees
@beeme1mr @toddbaert

Comments

@toddbaert
Copy link
Member

toddbaert commented Sep 29, 2022 •
edited by beeme1mr
Loading

As discussed in our Sept 29 community meeting, we'd like to solidify the spec and the SDKs. This may (or may not) involve releasing a 1.0 of each SDK, but will certainly involve adding some stability guarantees to the spec (see #139).

The timeline proposed is:

Oct 7th:

  • breaking changes are in for all SDKs, and SDKs are compliant with 0.5.0.
  • evaluation API and provider spec documents are marked Hardening

Oct 14th:

  • all providers updated with the SDK breaking changes, compliant with latest respective SDK

Oct 17th:

  • pending the successful updates of a majority of providers, we release SDKs with enhanced stability guarantees
  • this could mean SDKs release 1.0 versions, 1.0rcs, or perhaps just explicitly state they're ready for stability testing (interested in thoughts on this).

Note: The stability guarantees linked above do not prevent us from adding new features, just from breaking old ones. This effort is to provide assurances around the use of the existing interfaces, particularly providers and the application-author-facing Evaluation API.
@beeme1mr beeme1mr mentioned this issue Oct 4, 2022
Closed
@toddbaert toddbaert mentioned this issue Oct 13, 2022
Merged
toddbaert added a commit that referenced this issue Oct 17, 2022
@toddbaert
chore: section clarity, harden API, providers (#149)
c179236 
**Marking Evaluation API and Providers `hardening`** and a few
non-functional changes here that improve structure.

specifically:

- explicitly mark and number all sections
- section headings have consistent numbering (provider section numbering
was different than the other docs)
- removed "draft" language 

An alternative to marking all of `provider` and `evaluation API` as
hardening would be just marking all existing sections therein as
hardening, which might be better since we'd have to do that anyway if we
added a new experimental section.

see: #146 for more on release
goals.

Signed-off-by: Todd Baert <[email protected]>
@beeme1mr
Copy link
Member

beeme1mr commented Mar 7, 2023

The spec now has explicit stability guarantees and 1.0 SDKs have been released.

@beeme1mr beeme1mr closed this as completed Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beeme1mr beeme1mr

@toddbaert toddbaert

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@beeme1mr @toddbaert