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.

Sign up for GitHub

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

Jump to bottom

Documentation Improvements (v1.6 release cycle) #9216

Closed
2 tasks done
Prajyot-Parab opened this issue Aug 16, 2023 · 3 comments · Fixed by #9270
Closed
2 tasks done

Documentation Improvements (v1.6 release cycle) #9216

Prajyot-Parab opened this issue Aug 16, 2023 · 3 comments · Fixed by #9270
Assignees
@Prajyot-Parab
Labels
area/release Issues or PRs related to releasing kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Prajyot-Parab
Copy link
Contributor

Prajyot-Parab commented Aug 16, 2023 •
edited by sbueringer
Loading

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

  • Doc improvement (add a recommendation to leads tasks):Communicate and set clear expectations between the leads and the shadows about timeline and rotation.

    • Clearly communicate that we will aim for rotation of ownership.

  • Doc improvement: consider "public release session"

    • Suggestion: Start a zoom meeting and make it public. Let's kick start the process in the zoom meeting. If there is time to just wait for some process to complete, use the time to discuss any issues/questions or just hop back on when ready to continue.

/kind documentation
/area release
@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. area/release Issues or PRs related to releasing needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 16, 2023
@Prajyot-Parab
Copy link
Contributor Author

/assign @Prajyot-Parab

@sbueringer
Copy link
Member

/triage accepted

@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 Aug 16, 2023
@furkatgofurov7 furkatgofurov7 mentioned this issue Aug 17, 2023
Closed
35 tasks
@Prajyot-Parab Prajyot-Parab mentioned this issue Aug 17, 2023
Merged
@furkatgofurov7
Copy link
Member

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 22, 2023
@Prajyot-Parab Prajyot-Parab mentioned this issue Aug 22, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Prajyot-Parab Prajyot-Parab

Labels
area/release Issues or PRs related to releasing kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CAPI v1.6 release improvement tasks
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

📖 Documentation improvements: suggestions for team leads Prajyot-Parab/cluster-api
4 participants
@sbueringer @k8s-ci-robot @furkatgofurov7 @Prajyot-Parab