Add /me to the patch release and release managers team

[hoegaarden]

• I was removed from patch-release-team in this PR, I am not sure why. Re-adding myself again.
• I think I also need to be on release-managers to be able to actually cut a patch.

If there are good reasons why I have been removed in the first place, please let me know.

/cc @kubernetes/patch-release-team
/cc @kubernetes/release-managers
/cc @cblecker

[k8s-ci-robot]

Welcome @hoegaarden!

It looks like this is your first PR to kubernetes/org 🎉. 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/org 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. 😃

[hoegaarden]

/assign justaugustus

[cblecker]

You were removed as only active branch managers or patch release managers should be in these teams. According to the docs in https://git.k8s.io/sig-release, I see you were the 1.14 branch manager, but that release has already shipped.

[justaugustus]

@hoegaarden -- I had discussed with @cblecker (via DM) that this change should've been made separately from the changes in that PR, but I should've noted that publicly as well.

Christoph --
Approving this as Hannes will be a part of the official roster moving forward: https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#contact

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hoegaarden, justaugustus

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:

• config/kubernetes/sig-release/OWNERS [justaugustus]

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

[cblecker]

@justaugustus Thanks for the updated docs!

I have two asks:

• When the 1.15 dust settles, would you mind sending out a wider notice of this change? I don't remember seeing one go out to the whole project.
• Can you update the docs to note that if this team changes, you should explicitly reach out to the GitHub admin team? In addition to these teams, there's also things like k-security access that needs to be granted/updated.

[justaugustus]

@cblecker -- For sure. I'm actually writing a doc on Release Managers team structure right now.
Stay tuned! :)

[cblecker]

@justaugustus You're the best!

[justaugustus]

@cblecker -- No, no, you!