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

Z9r5 patch 1 #306

Closed
wants to merge 1 commit into from
Closed

Z9r5 patch 1 #306

wants to merge 1 commit into from

Conversation

z9r5
Copy link
Member

@z9r5 z9r5 commented May 7, 2024

Description

Why do we need it, and what problem does it solve?

Why do we need it in the patch release (if we do)?

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: <kebab-case of a module name> | <1st level dir in the repo>
type: fix | feature | chore
summary: <ONE-LINE of what effectively changes for a user>
impact: <what to expect for users, possibly MULTI-LINE>, required if impact_level is high ↓
impact_level: default | high | low

@z9r5 z9r5 closed this May 8, 2024
@z9r5 z9r5 deleted the z9r5-patch-1 branch May 8, 2024 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant