Define and implement the release cadence survey

[saschagrunert]

The release cadence KEP states that there is a necessity for a feedback survey about the implemented cadence change:

SIG Release will draft an experience survey and distribute it to k/dev) and include it in the release notes of the first three releases from which the new cadence has been applied. This survey will include questions around the release cadence and how it impacted end users and can be used to make a final decision regarding release cadence (i.e. promoting this KEP to stable).

Survey contents are to be determined, but we welcome content suggestions to continually improve the process.

The following questions have to be resolved before sending out the survey to the community:

• When should the survey be done?
  There are discussions about doing it late 2021 if we have enough data to collect.
• Which questions do we want to include?
  What is the outcome of the survey? For example, one target should be to be able to elaborate on alternative release
  models (releasing faster) for Kubernetes and verify if the current cadence is still the right one.

/priority important-longterm
/help

[k8s-ci-robot]

@saschagrunert:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

The release cadence KEP states that there is a necessity for a feedback survey about the implemented cadence change:

SIG Release will draft an experience survey and distribute it to k/dev) and include it in the release notes of the first three releases from which the new cadence has been applied. This survey will include questions around the release cadence and how it impacted end users and can be used to make a final decision regarding release cadence (i.e. promoting this KEP to stable).

Survey contents are to be determined, but we welcome content suggestions to continually improve the process.

The following questions have to be resolved before sending out the survey to the community:

• When should the survey be done?
  There are discussions about doing it late 2021 if we have enough data to collect.
• Which questions do we want to include?
  What is the outcome of the survey? For example, one target should be to be able to elaborate on alternative release
  models (releasing faster) for Kubernetes and verify if the current cadence is still the right one.

/priority important-longterm
/help

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.

[Damans227]

Hey @saschagrunert How are you ? I am shadowing on the K8s v1.22 release team. Can I help you with this issue ? Since, I am a new contributor, I would need some guidance and support from a senior person.

[saschagrunert]

Hey @saschagrunert How are you ? I am shadowing on the K8s v1.22 release team. Can I help you with this issue ? Since, I am a new contributor, I would need some guidance and support from a senior person.

Hey, thank you for jumping into this discussion! 🙏

I think the first step we can do is defining a set of questions we would like to ask. We could start iterating in a Google Doc to get further feedback from the community.

@Damans227, do you wanna start with that?

[Damans227]

@saschagrunert Sure, does it matter where I create this google doc ? Can I create it on my shared drive ? Also, apologies in advance, I am gonna have a fair share of noob questions.

[saschagrunert]

@saschagrunert Sure, does it matter where I create this google doc ? Can I create it on my shared drive ? Also, apologies in advance, I am gonna have a fair share of noob questions.

No worries, yeah it's totally fine if you share a doc (publicly) directly from your account. I'm happy to contribute and add a certain point we can put it into markdown and request more feedback from a broader group.

[Damans227]

I have created the new doc and it is publicly available to edit on this link:

https://docs.google.com/document/d/14d4P24BrL280IXgDsKzXX89UFsI0X275HGYT4RcrASU/edit?usp=sharing

Please feel free to make any necessary changes and share your feedback.

[saschagrunert]

Added some first thoughts 👍

[saschagrunert]

@Damans227 do you think that you could use my input to create some first questions?

[Damans227]

@Damans227 do you think that you could use my input to create some first questions?

Yes of-course. I will create a google form with questions around those ideas which you have shared. I should be able to get this done very shortly, likely by some time tomorrow evening. Thanks for following up.

[Damans227]

@saschagrunert Please take a look, and share your feedback.

https://docs.google.com/forms/d/15nhhCYjvy8cbV9ELEer9knwiFIcNwPT8ybfEwxTLyLo/edit?usp=sharing

[saschagrunert]

@saschagrunert Please take a look, and share your feedback.

https://docs.google.com/forms/d/15nhhCYjvy8cbV9ELEer9knwiFIcNwPT8ybfEwxTLyLo/edit?usp=sharing

Thanks, I think there is a commenting section when being able to edit the document. I requested access to do so.

[Damans227]

I have granted you the access to edit.

[saschagrunert]

I have granted you the access to edit.

This looks already really good! I added a question about the customer base/size. What do you think about this one?

[Damans227]

Yup, this looks good already and thanks for adding that question. It is not marked as required though, is that intentional ? Also, I haven't made Github handle question required as well, what do you think about that ?

[saschagrunert]

Yup, this looks good already and thanks for adding that question. It is not marked as required though, is that intentional ? Also, I haven't made Github handle question required as well, what do you think about that ?

Hm, I think we're fine having them optional.

[Damans227]

Ok, cool. Thanks for your feedback.

[saschagrunert]

I made some edits and gave the SIG Release leads editing permissions to give them a chance to make some edits. If we're fine with it, then we may move it over to survey monkey since this seems the tool of choice.

[saschagrunert]

/milestone v1.22

[saschagrunert]

@Damans227 do you wanna put the survey into surveymonkey or should I take care of it? :)

[Damans227]

I went ahead and implemented the survey into survey monkey. PTAL, https://www.surveymonkey.com/r/HF36WH7

[saschagrunert]

Thank you @Damans227! @kubernetes/sig-release-leads PTAL 👆

[k8s-triage-robot]

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/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 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

[saschagrunert]

/remove-lifecycle stale

[k8s-triage-robot]

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/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 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

[saschagrunert]

/remove-lifecycle stale

[saschagrunert]

Status update: We plan to push this survey out in the beginning of 2022

[k8s-triage-robot]

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/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 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

[saschagrunert]

@Damans227 can you please add myself to the survey that I'm able to see the results? My account is saschagrunert.

[saschagrunert]

Mail sent: https://groups.google.com/a/kubernetes.io/g/dev/c/5Sj-Mk0_I1Y

[Damans227]

https://www.surveymonkey.com/r/HF36WH7

Yes, of course. I am working on this now.

[Damans227]

@saschagrunert So, it looks like I can not add you to my "team" on survey monkey and give you the access to its results without upgrading to a paid plan. The only option available to share the survey data in free tier is to generate a public link and publish the responses online.

[saschagrunert]

@saschagrunert So, it looks like I can not add you to my "team" on survey monkey and give you the access to its results without upgrading to a paid plan. The only option available to share the survey data in free tier is to generate a public link and publish the responses online.

Sounds good, let's revisit the survey from time to time and probably close it by the end of the cycle :) Then we can evaluate the results.

[jberkus]

Hey, all, I'm going to ask you to pull the survey and use Kubernetes' official survey account for it. Also there's a few other things missing like GDPR headers.

[jberkus]

Also --- we can have contributor-comms publicize the survey.

[Damans227]

Hey, all, I'm going to ask you to pull the survey and use Kubernetes' official survey account for it. Also there's a few other things missing like GDPR headers.

I have taken the survey down, as stated in the slack. Thanks!

[jberkus]

Drafting replacement with Sascha and Damans

[jberkus]

Survey is running now: https://www.surveymonkey.com/r/k8s-cadence-2022

[saschagrunert]

The release cadence survey is now closed.

Summary

87 People answered the questions