You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
This has been raised up in the community meeting when we discussed #24.
Since spec is relatively stable, we want to validate ideas before making changes to spec. Usually we model some runtime functionalities as traits at first stage and then gradually move them into the spec. As a common practice, we need to agree on a standard experimental APIGroup for these kind of system/runtime traits.
My proposal is experimental.core.oam.dev/v1alpha2, where core.oam.dev/v1alpha2 matches the spec version and we add experimental prefix.
The text was updated successfully, but these errors were encountered:
This has been raised up in the community meeting when we discussed #24.
Since spec is relatively stable, we want to validate ideas before making changes to spec. Usually we model some runtime functionalities as traits at first stage and then gradually move them into the spec. As a common practice, we need to agree on a standard experimental APIGroup for these kind of system/runtime traits.
My proposal is
experimental.core.oam.dev/v1alpha2
, wherecore.oam.dev/v1alpha2
matches the spec version and we addexperimental
prefix.The text was updated successfully, but these errors were encountered: