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.

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

Zeebe command binding component as stable #2941

Closed
alicejgibbons opened this issue Jun 28, 2023 · 3 comments
Closed

Zeebe command binding component as stable #2941

alicejgibbons opened this issue Jun 28, 2023 · 3 comments
Assignees
Labels
good first issue Good for newcomers kind/enhancement New feature or request P1 pinned Issue does not get stale
Milestone

Comments

@alicejgibbons
Copy link

Describe the feature

Zeebe command output binding component requires certification tests to be moved from Alpha to Beta to Stable.
https://docs.dapr.io/reference/components-reference/supported-bindings/zeebe-command/

Release Note

RELEASE NOTE: ADD Zeebe command binding component as stable.

@alicejgibbons alicejgibbons added the kind/enhancement New feature or request label Jun 28, 2023
@artursouza artursouza added this to the v1.12 milestone Jun 28, 2023
@artursouza artursouza added P1 pinned Issue does not get stale good first issue Good for newcomers labels Jun 28, 2023
@cicoyle
Copy link
Contributor

cicoyle commented Sep 5, 2023

Current status = Alpha. Desire to move to Beta then Stable.

Beta requirements:

  • The component must pass all the component conformance tests defined to satisfy the component specification
  • The component conformance tests have been run in a Dapr maintainers managed environment
  • The component contains a record of the conformance test result reviewed and approved by Dapr maintainers with specific components-contrib version --NOTE: marked this as true according to add zeebe command & jobworker yaml for conformance tests #3117
  • Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases

Stable requirements:

  • The component must have component certification tests validating functionality and resiliency
  • The component is maintained by Dapr maintainers and supported by the community
  • The component is well documented and tested
  • The component has been available as Alpha or Beta for at least 1 minor version release of Dapr runtime prior
  • A maintainer will address component security, core functionality and test issues according to the Dapr support policy and issue a patch release that includes the patched stable component

Once this WIP PR to migrate Zeebe e2e tests to certification tests is completed & merged, then the Stable requirements can likely be completed. -->now merged

@cicoyle
Copy link
Contributor

cicoyle commented Sep 11, 2023

/assign

@berndverst
Copy link
Member

Ideally this issue is assigned to @akkie because he did the main work to make this happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/enhancement New feature or request P1 pinned Issue does not get stale
Projects
None yet
Development

No branches or pull requests

4 participants