-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 release: restructure release docs team roles #10651
Conversation
Welcome @dhij! |
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 Once the patch is verified, the new status will be reflected by the 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. |
/area documentation |
/ok-to-test |
da82f2d
to
2e8b9d7
Compare
9bb6435
to
c032422
Compare
@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 |
- [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) |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
docs/release/release-team.md
Outdated
|
||
* 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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 👍
docs/release/release-team.md
Outdated
**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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
@dhij Do you have time to address the findings above? |
@sbueringer 👋 sorry for the delay, yes i will get to it 🙂 |
d356ac5
to
9ae96b5
Compare
@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 |
/lgtm Will do a small PR on-top after merging. |
LGTM label has been added. Git tree hash: 316e95aa40995625d83deca3c0aea380fec97293
|
[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 |
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