Achieve decision: What would be an ideal length for a K8s promotion?

kubernetes-sigs / promo-tools

Container and file artifact promotion tooling for the Kubernetes project

Apache License 2.0

145 stars 71 forks source link

Open lasomethingsomething opened 12 months ago

lasomethingsomething commented 12 months ago

This is a problem for the official k8s releases. Not the subprojects of the K8S project.

By 1-3 contributors:

[ ] Do research on the topic
[ ] Collect questions from SIG members as part of your research phase
[ ] Prepare a brief (1-2 pages max) proposal evaluating pros, cons, and tradeoffs
[ ] Share proposal with SIG (mailing list, Slack thread, at community meeting) By the SIG/group:
[ ] SIG members provide input on findings/raise questions
[ ] After a timeboxed review period (to be determined), SIG members regroup to make a decision
[ ] Log decision for community awareness
[ ] Plan next steps

k8s-triage-robot commented 8 months 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:

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

/lifecycle stale

xmudrii commented 8 months ago

/remove-lifecycle stale

k8s-triage-robot commented 5 months 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:

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

/lifecycle stale

xmudrii commented 5 months ago

/remove-lifecycle stale

k8s-triage-robot commented 2 months 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:

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

/lifecycle stale

xmudrii commented 2 months ago

/remove-lifecycle stale