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

Fixed typo in the release lead handbook #2616

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sreeram-venkitesh
Copy link
Member

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Fixes a typo in the release lead handbook.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 10, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sreeram-venkitesh
Once this PR has been reviewed and has the lgtm label, please assign cici37 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the area/release-team Issues or PRs related to the release-team subproject label Sep 10, 2024
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. needs-priority size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 10, 2024
@@ -93,7 +93,7 @@ Release Team selection should happen in accordance with the [Release Team select
- Enhancements tracking spreadsheet: `http://bit.ly/k8sXYY-enhancement-tracking`
- Merged PRs with release notes: `http://bit.ly/k8sXYY-relnotes`
- Use the same conventions for additional documents
- Burndown meetings happen at 10AM Pacific Time, and you invite the and the Kubernetes Release calendar (`[email protected]`) to them.
- Burndown meetings happen at 10AM Pacific Time, and you invite the release team members and the Kubernetes Release calendar (`[email protected]`) to them.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can also update this to mention only inviting the release calendar if that makes more sense.

Suggested change
- Burndown meetings happen at 10AM Pacific Time, and you invite the release team members and the Kubernetes Release calendar (`[email protected]`) to them.
- Burndown meetings happen at 10AM Pacific Time, and you invite the Kubernetes Release calendar (`[email protected]`) to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-team Issues or PRs related to the release-team subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants