Closed toddbaert closed 2 years ago
Name | Link |
---|---|
Latest commit | 2e0e47b3978050097bf63b650938c04444fe339e |
Latest deploy log | https://app.netlify.com/sites/lucky-creponne-baf9b3/deploys/63582ef3d7071c000974a8e3 |
Deploy Preview | https://deploy-preview-160--lucky-creponne-baf9b3.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Additionally, this is a preemptive PR, correct? In anticipation of the 1.0 spec release? Asking since I still don't see a 1.0 in the spec repo :slightly_smiling_face:
If 0.5.0
is essentially 1.0
that would be good to know as well
Additionally, this is a preemptive PR, correct? In anticipation of the 1.0 spec release? Asking since I still don't see a 1.0 in the spec repo slightly_smiling_face
If
0.5.0
is essentially1.0
that would be good to know as well
We are not doing a 1.0 release of the spec, but have added hardening
labels to certain subsections. Only the mentioned SDKs are 1.0 (2/4 thus far, but hopefully it's 4/4 soon). Should we add clarification on that?
I want to find a 3rd bullet point for the experimental sdk features. Also, "hardening" sounds almost stable but not actually stable. Can it regress? If not, we should find a better name. If so, we should mention it. :)
I want to find a 3rd bullet point for the experimental sdk features.
I'm sure I can think of one.
Also, "hardening" sounds almost stable but not actually stable. Can it regress? If not, we should find a better name. If so, we should mention it. :)
The "hardening" language was agreed on here: https://github.com/open-feature/spec/pull/139. It can't be regressed; we agreed we wanted a unidirectional graduation.
I'm open to changing the term if the meaning doesn't change. Any proposals?
@justinabrahms
This works for me. Re read that post and it's about which version number changes on update, which works for me.
@justinabrahms
I've added one more point to the experimental features. Right now, we have 4 sections in the SDK, 2 of which are hardening
and 2 of which are sill experimental
. The point I've added is "experimental context propagation" (passing context attrs on the async continuation or thread-local storage, etc) which is currently only implemented experimentally in the JS-SDK.
Add blog post about 1.0 and spec stabilization.
Direct preview link: https://deploy-preview-160--lucky-creponne-baf9b3.netlify.app/blog