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

📖 Add Maintainer to release team roles #8988

Merged

Conversation

killianmuldoon
Copy link
Contributor

Add a Release Writer role to the the release tasks doc. This role has become de facto required as part of the release process. This change formalizes the role and defines the responsibilities and tasks of someone who is the designated Release Writer for a release.

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 11, 2023
@killianmuldoon
Copy link
Contributor Author

/area release

@k8s-ci-robot k8s-ci-robot added area/release Issues or PRs related to releasing size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 11, 2023
@joekr
Copy link
Member

joekr commented Jul 11, 2023

/lgtm

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

LGTM label has been added.

Git tree hash: 75d023e3ca78cacb519f49aa5598cea3997238de

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 11, 2023
@k8s-ci-robot k8s-ci-robot requested a review from joekr July 11, 2023 12:43
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 11, 2023
@killianmuldoon killianmuldoon force-pushed the pr-add-release-writer branch 4 times, most recently from 462fb9b to 4e0de00 Compare July 11, 2023 12:56
Copy link
Contributor Author

@killianmuldoon killianmuldoon left a comment

Choose a reason for hiding this comment

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

/retitle 📖 Add Release Writer to release team roles

@k8s-ci-robot k8s-ci-robot changed the title [WIP] 📖 Add Release Writer to release team roles 📖 Add Release Writer to release team roles Jul 11, 2023
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 11, 2023
@killianmuldoon
Copy link
Contributor Author

/hold

For feedback from the community meeting.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 11, 2023
@elmiko
Copy link
Contributor

elmiko commented Jul 12, 2023

we are discussing this during the community meeting on 12 July, there are some questions about this process and the name. cc @CecileRobertMichon for more comments.

re: naming, "release maintainer" as opposed to "release writer" might make this clearer

@CecileRobertMichon
Copy link
Contributor

TLDR from the office hours discussion:

  • general consensus that having a maintainer available for help and support during release days is a good idea, +1 to formalize this
  • we should still look into giving the release team all the permissions they need to be able to release end to end without needing maintainers' help (this might mean setting up more automation, setting up a release manager team similar to k8s with a custom github role, etc.)
  • Preference around naming this role something like "on-call maintainer" or "supporting maintainer" so it's clear this role has to be filled by a project maintainer as opposed to something generic like "release writer"

Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

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

Only a nitpick on the role name otherwise +1 for me

docs/release/release-tasks.md Outdated Show resolved Hide resolved
Copy link
Member

@sbueringer sbueringer left a comment

Choose a reason for hiding this comment

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

Just nits

docs/release/release-tasks.md Outdated Show resolved Hide resolved
docs/release/release-tasks.md Show resolved Hide resolved
docs/release/release-tasks.md Outdated Show resolved Hide resolved
docs/release/release-tasks.md Outdated Show resolved Hide resolved
docs/release/release-tasks.md Outdated Show resolved Hide resolved
docs/release/release-team.md Outdated Show resolved Hide resolved
docs/release/release-team.md Outdated Show resolved Hide resolved
@sbueringer
Copy link
Member

sbueringer commented Jul 13, 2023

/lgtm
You'll need a rebase now though

Thx for keeping this documentation up-to-date!!!

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

LGTM label has been added.

Git tree hash: 341f271e925c22ce4a1ab1b0018e8c24c404e505

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 13, 2023
Signed-off-by: killianmuldoon <kmuldoon@vmware.com>
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 13, 2023
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 13, 2023
@sbueringer sbueringer changed the title 📖 Add Release Writer to release team roles 📖 Add Maintainer to release team roles Jul 14, 2023
@sbueringer
Copy link
Member

sbueringer commented Jul 14, 2023

/lgtm

Let's give others a chance to review (again). Would be good if we can get this merged within the next week or so. So we have it ready for the next cycle.

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

LGTM label has been added.

Git tree hash: c76217f83eafd32ca07abd91fea276754207145b

@killianmuldoon
Copy link
Contributor Author

killianmuldoon commented Jul 18, 2023

/hold cancel

@sbueringer WDYT about merging this as-is? If there's further feedback we can update before the next release team comes onboard.

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 18, 2023
@sbueringer
Copy link
Member

Sounds good.

If there is any further feedback, please let us know and we can do a follow-up PR

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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 Jul 18, 2023
@k8s-ci-robot k8s-ci-robot merged commit 13d90f9 into kubernetes-sigs:main Jul 18, 2023
20 of 21 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.6 milestone Jul 18, 2023
| CI Signal/Bug Triage/Automation Manager | TBD | TBD |
| Release Writer | TBD | TBD |
Copy link
Contributor

Choose a reason for hiding this comment

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

sorry for the late review! this should also be renamed to Maintainer

otherwise LGTM

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for catching that - opened a PR at #9013

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/release Issues or PRs related to releasing 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants