Release Manager access for @mehabhalodiya

kubernetes / sig-release

Repo for SIG release

Apache License 2.0

521 stars 379 forks source link

Release Manager access for @mehabhalodiya #2429

Open mehabhalodiya opened 5 months ago

mehabhalodiya commented 5 months ago

GitHub Username

e.g., @mehabhalodiya

Release Manager role

e.g., Release Manager Associate

Tenure

temporary: Meha is a Release Manager Associate being granted temporary elevated access to cut releases. Access should be revoked after the v1.30 release cycle is complete.

Release Manager Onboarding

All pull requests within these checklists should be marked with an explicit hold and only released once approved by a Release Engineering subproject owner.

[x] Addition of a new Release Manager has been discussed with and approved by Release Engineering subproject owners
[x] Ensure new Release Manager:
- [x] Has joined the following mailing lists:
- kubernetes-sig-release
- kubernetes-dev
- [x] Has joined the following Slack channels:
- #sig-release
- #release-management
- [x] Is a Kubernetes GitHub org member
[ ] Update Release Managers page to include the new Release Manager
[ ] Update the cherry_pick_approved prow plugin configuration section to contain the new approver.

Temporary Access

cc: @kubernetes/release-engineering

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

saschagrunert commented 1 month ago

@mehabhalodiya is this done?

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten