sig-release icon indicating copy to clipboard operation
sig-release copied to clipboard
verified publisher icon kubernetes

[Tracking Issue] GitHub Issue Checklists for Role Lead Progress during a Release Cycle

Open Priyankasaggu11929 opened this issue 2 years ago • 4 comments

This GitHub issue is to track creating task checklists for the Release Team's sub-team Role Leads (and their shadows), in order to help them manage their tasks and responsibilities efficiently during a release cycle.

The purpose of these checklists is to break down all the responsibilities of a Role Lead throughout the 14 weeks of a release cycle into individual tasks. This way, we ensure transparency, avoid any oversights, provide timely help/support and make sure everyone stays informed and aligned.

These checklists will resemble what we currently use, to track the Release Team Lead's progress during a release cycle - [1.29] Release Team Lead Cycle Progress.

Definition of Done:

create checklist templates for the following roles:

  • [ ] Comms – @krol3 / TBD shadow, @mickeyboxell / @ramrodo )
  • [ ] Docs – (@katcosgrove / TBD shadow, @mickeyboxell)
  • [ ] Enhancements – (@npolshakova / TBD shadow, @Priyankasaggu11929)
  • [ ] Release Notes – (@fsmunoz / TBD shadow, @ramrodo)
  • [ ] Release Signal – (@Vyom-Yadav / TBD shadow, @mehabhalodiya / @neoaggelos)

cc: @kubernetes/release-team-leads, @kubernetes/sig-release-leads

Priyankasaggu11929 avatar Sep 16 '23 05:09 Priyankasaggu11929

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

k8s-triage-robot avatar Jan 28 '24 18:01 k8s-triage-robot

/remove-lifecycle stale

Priyankasaggu11929 avatar Jan 29 '24 05:01 Priyankasaggu11929

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

k8s-triage-robot avatar Apr 28 '24 05:04 k8s-triage-robot

/remove-lifecycle stale

Priyankasaggu11929 avatar Apr 29 '24 11:04 Priyankasaggu11929

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

k8s-triage-robot avatar Jul 28 '24 11:07 k8s-triage-robot