Skip to content

Identify v1Beta1 API candidates and potential gaps #1869

@akashrv

Description

@akashrv

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

  • Identify minimal set of APIs that will be part of v1beta1 api surface
  • Identify what is missing for each construct and have issues
  • Target v1beta1 apis in or before v0.11

Metadata

Metadata

Assignees

Labels

EpicEpics to group issueskind/feature-requestpriority/important-soonMust 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 release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions