kubernetes-retired / contributor-tweets

Repo for automating tweets to the K8sContributor twitter account owned by the k8s Contributor Comms Team within SIG-contribex (https://github.com/kubernetes/community/tree/master/communication/contributor-comms)).
https://twitter.com/K8sContributors
Apache License 2.0
13 stars 29 forks source link

1.26 Enhancements Board Update #263

Closed gracenng closed 2 years ago

gracenng commented 2 years ago

Provide the actual tweet content between the commented colons

🚧 Changes to the v1.26 release opt-in process 🚧

The enhancements sheet with be replaced with an automated Github board. SIG lead only, apply lead-opt-in label on KEPs to opt-in.

Find us on Slack at release-enhancements for help!

cc @reylejano @rhockenbury @leonardpahlke

github-actions[bot] commented 2 years ago

A new file has been created with your tweet content. Please refer the below linked PR

gracenng commented 2 years ago

Enhancements tracking migration: https://github.com/kubernetes/sig-release/issues/2009

reylejano commented 2 years ago

@gracenng I think there is a typo:

🚧 Changes to the v1.26 release opt-in process 🚧

The enhancements sheet with will be replaced with an automated Github board. SIG lead only, apply lead-opt-in label on KEPs to opt-in.

reylejano commented 2 years ago

(non-blocking) Also suggest something like:

📣 Changes to the v1.26 release enhancements opt-in process 📣 For 1.26, the enhancements sheet is replaced with a Github projects board. To opt-in for 1.26, SIG leads apply the lead-opt-in label on the KEP issue.

/cc @palnabarun @rhockenbury @leonardpahlke @gracenng

leonardpahlke commented 2 years ago

I like this suggestion. I would send the tweet out after we send the email. Then we could include a link in the email that gives more details.