-
Notifications
You must be signed in to change notification settings - Fork 630
Identify v1Beta1 API candidates and potential gaps #1869
Copy link
Copy link
Closed
Labels
EpicEpics to group issuesEpics to group issueskind/feature-requestpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.proposal/0.12Proposed (not planned) work items for 0.12 releaseProposed (not planned) work items for 0.12 release
Milestone
Metadata
Metadata
Labels
EpicEpics to group issuesEpics to group issueskind/feature-requestpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.proposal/0.12Proposed (not planned) work items for 0.12 releaseProposed (not planned) work items for 0.12 release
Problem
We need to figure out v1beta1 api surface for Knative Eventing. We could either start moving stable apis to v1beta1, or identify a minimum set of apis that make sense to promote together to v1beta1 and identify what is missing so that we can target to fill the gaps in v0.10 and promote to v1beta1 in v0.11
Exit Criteria