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

Define details of "Communicate key dates to the community" #9638

Closed
furkatgofurov7 opened this issue Oct 30, 2023 · 1 comment · Fixed by #9590
Closed

Define details of "Communicate key dates to the community" #9638

furkatgofurov7 opened this issue Oct 30, 2023 · 1 comment · Fixed by #9590
Assignees
Labels
area/release Issues or PRs related to releasing triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@furkatgofurov7
Copy link
Member

What would you like to be added (User Story)?

Part of Improvement tasks for v1.6 release cycle #9104

Detailed Description

We need to better define Information/communication channels/stakeholders and remove TBDs' from release-tasks doc

Anything else you would like to add?

No response

Label(s) to be applied

/area release

@k8s-ci-robot k8s-ci-robot added area/release Issues or PRs related to releasing needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 30, 2023
@furkatgofurov7
Copy link
Member Author

/triage accepted
/assign

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release Issues or PRs related to releasing triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants