sig-release
sig-release copied to clipboard
kubernetes
Update documentation: use release-team-shadow-stats at the start of the release-cycle 1.25
What would you like to be added:
- Update the documentation (lead handbook) to mention the release-team-shadow-stats project to create applicant summaries for release-team role leads (see output examples). The output markdown files should help how to consume applicant information (instead of reading a excel table you can read a markdown file)
- Update documentation release team selection to mention the project release-team-shadow-stats
- Update the release timeline to publish the release-team shadow applicant report in the first week of the release (the report is currently tbd, see issue: https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/8) - timeline for 1.24
Why is this needed:
The release-team-shadow-stats aims to improve transparency (with the report (see example raw charts) and how to consume applicant information (no changes to the selection criteria!) instead of a excel file with all applicants every release team role-lead you receive a formatted markdown file (see examples)
ref tracking issue: https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/4
/milestone v1.24
@leonardpahlke: The provided milestone is not valid for this repository. Milestones in this repository: [next, v.1.25, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]
Use /milestone clear to clear the milestone.
In response to this:
What would you like to be added:
- Update the documentation (lead handbook) to mention the release-team-shadow-stats project to create applicant summaries for release-team role leads (see output examples). The output markdown files should help how to consume applicant information (instead of reading a excel table you can read a markdown file)
- Update documentation release team selection to mention the project release-team-shadow-stats
- Update the release timeline to publish the release-team shadow applicant report in the first week of the release (the report is currently tbd, see issue: https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/8) - timeline for 1.24
Why is this needed:
The release-team-shadow-stats aims to improve transparency (with the report (see example raw charts) and how to consume applicant information (no changes to the selection criteria!) instead of a excel file with all applicants every release team role-lead you receive a formatted markdown file (see examples)
ref tracking issue: https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/4
/milestone 1.24
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/test-infra repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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/test-infra repository.