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

📖 release: restructure release docs team roles #10651

Merged
merged 11 commits into from
Aug 20, 2024

Conversation

dhij
Copy link
Contributor

@dhij dhij commented May 21, 2024

What this PR does / why we need it:

This PR breaks up the lengthy release tasks doc by team as suggested in #10354

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #10354

Copy link

linux-foundation-easycla bot commented May 21, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/needs-area PR is missing an area label labels May 21, 2024
@k8s-ci-robot
Copy link
Contributor

Welcome @dhij!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 21, 2024
@k8s-ci-robot
Copy link
Contributor

Hi @dhij. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 21, 2024
@dhij
Copy link
Contributor Author

dhij commented May 21, 2024

/area documentation

@k8s-ci-robot k8s-ci-robot added area/documentation Issues or PRs related to documentation and removed do-not-merge/needs-area PR is missing an area label labels May 21, 2024
@chrischdi
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 21, 2024
@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 21, 2024
@dhij dhij force-pushed the dhij/restructure-release-doc branch from da82f2d to 2e8b9d7 Compare June 2, 2024 11:32
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jun 2, 2024
@dhij dhij force-pushed the dhij/restructure-release-doc branch from 9bb6435 to c032422 Compare June 2, 2024 12:24
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 2, 2024
@dhij
Copy link
Contributor Author

dhij commented Jun 2, 2024

@chrischdi I fixed the broken links and would appreciate if you could have a look 🙏

When this PR gets merged, I will need a follow-up PR to fix a bunch of broken links to release-tasks.md since that file would no longer exist (ex. in .github/ISSUE_TEMPLATE). I saw that including those link changes in this PR will break the CI since those are absolute https:// links.

@dhij dhij requested a review from chrischdi June 2, 2024 12:34
- [Tasks](#tasks)
- [Finalize release schedule and team](#finalize-release-schedule-and-team)
- [Add/remove release team members](#addremove-release-team-members)
- [Prepare main branch for development of the new release](#prepare-main-branch-for-development-of-the-new-release)
Copy link
Member

Choose a reason for hiding this comment

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

Doesn't this TOC miss items which are there? e.g.
Optional] Track Release and Improvement tasks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for pointing that out, I addressed this in my most recent commits.


* The examples in these documents are based on the v1.6 release cycle.
* The documents focus on tasks that are done for every release. One-time improvement tasks are out of scope.
* If a task is prefixed with `[Track]` it means it should be ensured that this task is done, but the folks with the corresponding role are not responsible to do it themselves.
Copy link
Member

Choose a reason for hiding this comment

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

Should we have this note in each handbook?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I moved this bullet point to each of the handbooks in my most recent commits 👍

**Notes**:

* The examples in these documents are based on the v1.6 release cycle.
* The documents focus on tasks that are done for every release. One-time improvement tasks are out of scope.
Copy link
Member

Choose a reason for hiding this comment

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

Does this still make sense as is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I removed this line as it is not relevant anymore.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 7, 2024
@sbueringer
Copy link
Member

@dhij Do you have time to address the findings above?

@dhij
Copy link
Contributor Author

dhij commented Aug 15, 2024

@sbueringer 👋 sorry for the delay, yes i will get to it 🙂

@dhij dhij force-pushed the dhij/restructure-release-doc branch from d356ac5 to 9ae96b5 Compare August 16, 2024 01:29
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 16, 2024
@dhij dhij requested a review from chrischdi August 16, 2024 01:31
@dhij
Copy link
Contributor Author

dhij commented Aug 16, 2024

@chrischdi @sbueringer 👋 i addressed your comments and would appreciate another review 🙏

There were 3 new commits to the release-task.md in the meantime and since the release-task.md file is removed as part of this PR, I had to manually cherry-pick the changes into the new role-handbooks docs accordingly.

@chrischdi
Copy link
Member

/lgtm
/approve

Will do a small PR on-top after merging.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 20, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 316e95aa40995625d83deca3c0aea380fec97293

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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

The pull request process is described 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2024
@k8s-ci-robot k8s-ci-robot merged commit 3abe305 into kubernetes-sigs:main Aug 20, 2024
21 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.9 milestone Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/documentation Issues or PRs related to documentation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Restructure release docs stack
4 participants