search

kubernetes / sig-release

Repo for SIG release
Apache License 2.0
544 stars 393 forks source link

Kubernetes v1.30 Major Themes contact #2428

Closed rashansmith closed 3 months ago

rashansmith commented 9 months ago

The release notes team will use this issue to track the work on nudging SIGs for entries on major themes for the v1.30 release cycle.

The Slack channel for each SIG is usually #sig-, but accurate links are available in k/community under sig-list.md. The plan is to ask for responses on the public Slack channel (non-disruptively).

Following is a bootstrap template that you can use to reach out to the individual sigs informing them about the https://github.com/kubernetes/sig-release/discussions/2424 discussion thread:

Hello SIG <sig-name>,

Major themes are an essential part of the Kubernetes release cycle as they provide a birds-eye view of major improvements that are coming as part of the upcoming release. 

As part of the effort aimed towards collecting the Major Themes for the v1.30 cycle, the release notes team is working towards gathering major themes entries. If you have anything to call out, we would appreciate it if your SIG can submit the content in
[Kubernetes 1.30 Major Themes GitHub discussion](https://github.com/kubernetes/sig-release/discussions/2424)

Ideally, we would like this to be completed by **Tuesday 19th March 2024**.

Thank you!

Different SIGs have a different number of tracked enhancements. Some SIGs have activities that aren't quite coupled with Kubernetes releases, but it's worth checking anyway in case there are things worth calling out in what they did between the previous release and the current release. One example is Dockershim removal from 1.24 or Immutable Secrets and ConfigMaps from the 1.21 release.

In this release, I've split up the number of SIGs based on a mix of those that have tracked enhancements, and those that do not, in order to provide a balanced group of options: each shadow should pick a group, I'll start with the first one, which includes some extra to make sure that each shadow has the same number - please select the group in the comments and I'll update this list.

Group 1 @rashansmith

Group 2 @OrlinVasilev

Group 3 @npolshakova

Group 4 @fykaa

Group 5 @satyampsoni

We'll try to keep the list up-to-date, but please double-check in the comments if someone has contacted their channel. We can debate more details in Slack.

/assign @fykaa @npolshakova @OrlinVasilev @satyampsoni

cc @katcosgrove @gracenng

/milestone v1.30

xref: https://github.com/kubernetes/sig-release/issues/2351

npolshakova commented 9 months ago

I can reach out to group 3!

fykaa commented 9 months ago

I'll pick Group 4

satyampsoni commented 9 months ago

I'll go for Group 5

OrlinVasilev commented 9 months ago

Group 2 @rashansmith - Done

[X] API Machinery [X] Scheduling [X] Autoscaling [X] Security

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:

You can:

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

/lifecycle stale

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 3 months ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 3 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/sig-release/issues/2428#issuecomment-2307942791): >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/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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.