From e1d99fc085646bab72e7b7497ee732b274eb0b26 Mon Sep 17 00:00:00 2001 From: Agustina Barbetta Date: Mon, 31 Mar 2025 17:14:04 -0300 Subject: [PATCH 1/4] Add ready-for-review deadline reminder template --- ...in-message.md => feature-blog-messages.md} | 23 +++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) rename release-team/role-handbooks/communications/templates/{feature-blog-opt-in-message.md => feature-blog-messages.md} (84%) diff --git a/release-team/role-handbooks/communications/templates/feature-blog-opt-in-message.md b/release-team/role-handbooks/communications/templates/feature-blog-messages.md similarity index 84% rename from release-team/role-handbooks/communications/templates/feature-blog-opt-in-message.md rename to release-team/role-handbooks/communications/templates/feature-blog-messages.md index 338f66da1b1..ea13e176a12 100644 --- a/release-team/role-handbooks/communications/templates/feature-blog-opt-in-message.md +++ b/release-team/role-handbooks/communications/templates/feature-blog-messages.md @@ -1,4 +1,6 @@ -# Initial Reach-out +# Feature Blog Opt-in + +## Initial Reach-out This is a message to send to enhancement owners to opt in to write a feature blog for their enhancement, it should be sent on the KEP issue. After this message is sent, the Comms team will follow up with the enhancement owner to help them keep in mind the timeline for the feature blog, every 1-2 weeks. @@ -64,7 +66,7 @@ With this one, you'd need to update the following placeholders: - `<> WEEKDAY, DAY MONTH`: Deadline for the Feature Blogs being ready for review, which is usually on week 13 - `LINK`: Add a link to the release document, such as `https://github.com/kubernetes/sig-release/tree/master/releases/release-1.33#timeline` -# Follow-up +## Follow-up ``` Hi @xx 👋, x.yy Communications Team here again! @@ -90,3 +92,20 @@ With this one, you'd need to update the following placeholders: - `<> WEEKDAY, DAY MONTH`: Deadline for the Feature Blogs being ready for review, which is usually on week 13 - `LINK`: Add a link to the release document, such as `https://github.com/kubernetes/sig-release/tree/master/releases/release-1.33#timeline` +# Feature Blog PR + +## "ready for review" deadline reminder +This is a message to send Feature Blog authors in their Feature Blog PR if they haven't marked it as "ready for review" days before the deadline. +``` +Hi @xx 👋 -- this is YOURNAME (@your_github_id) from the x.yy Communications Team! + +Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: **<> WEEKDAY, DAY MONTH**. By this deadline, your blog should be complete with all content finalized for review. If you are still working on it, please prioritize finishing it by the deadline mentioned above. + +If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you! +``` +In this template, you'd need to update the following placeholders: +- `@xx`: Mention Feature Blog PR author(s) +- `YOURNAME`: Your name, as you prefer +- `your_github_id`: Your GitHub ID +- `x.yy`: The upcoming Kubernetes version, such as 1.33, 1.34, etc. +- `<> WEEKDAY, DAY MONTH`: Deadline for the Feature Blogs being ready for review, which is usually on week 13 From e68511b9071344c37463fe3703b8e6709f8fbbdc Mon Sep 17 00:00:00 2001 From: Agustina Barbetta Date: Sun, 4 May 2025 17:15:34 -0300 Subject: [PATCH 2/4] Update release-team/role-handbooks/communications/templates/feature-blog-messages.md Co-authored-by: Ryota --- .../communications/templates/feature-blog-messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/release-team/role-handbooks/communications/templates/feature-blog-messages.md b/release-team/role-handbooks/communications/templates/feature-blog-messages.md index ea13e176a12..6449a39ad24 100644 --- a/release-team/role-handbooks/communications/templates/feature-blog-messages.md +++ b/release-team/role-handbooks/communications/templates/feature-blog-messages.md @@ -107,5 +107,5 @@ In this template, you'd need to update the following placeholders: - `@xx`: Mention Feature Blog PR author(s) - `YOURNAME`: Your name, as you prefer - `your_github_id`: Your GitHub ID -- `x.yy`: The upcoming Kubernetes version, such as 1.33, 1.34, etc. +- `vX.yy`: The upcoming Kubernetes version, such as v1.33, v1.34, etc. - `<> WEEKDAY, DAY MONTH`: Deadline for the Feature Blogs being ready for review, which is usually on week 13 From 2c6e4f6434eb44534a6cb10cbb64ae10c6c45eac Mon Sep 17 00:00:00 2001 From: Agustina Barbetta Date: Sun, 4 May 2025 17:15:50 -0300 Subject: [PATCH 3/4] Update release-team/role-handbooks/communications/templates/feature-blog-messages.md Co-authored-by: Ryota --- .../communications/templates/feature-blog-messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/release-team/role-handbooks/communications/templates/feature-blog-messages.md b/release-team/role-handbooks/communications/templates/feature-blog-messages.md index 6449a39ad24..7ed6b329bfd 100644 --- a/release-team/role-handbooks/communications/templates/feature-blog-messages.md +++ b/release-team/role-handbooks/communications/templates/feature-blog-messages.md @@ -97,7 +97,7 @@ With this one, you'd need to update the following placeholders: ## "ready for review" deadline reminder This is a message to send Feature Blog authors in their Feature Blog PR if they haven't marked it as "ready for review" days before the deadline. ``` -Hi @xx 👋 -- this is YOURNAME (@your_github_id) from the x.yy Communications Team! +Hi @xx 👋 -- this is YOURNAME (@your_github_id) from the vX.yy Communications Team! Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: **<> WEEKDAY, DAY MONTH**. By this deadline, your blog should be complete with all content finalized for review. If you are still working on it, please prioritize finishing it by the deadline mentioned above. From 6a7b9c6b60b6706d469816b7466ea90aa8dedc5d Mon Sep 17 00:00:00 2001 From: Agustina Barbetta Date: Sun, 4 May 2025 17:16:43 -0300 Subject: [PATCH 4/4] Update release-team/role-handbooks/communications/templates/feature-blog-messages.md Co-authored-by: Ryota --- .../communications/templates/feature-blog-messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/release-team/role-handbooks/communications/templates/feature-blog-messages.md b/release-team/role-handbooks/communications/templates/feature-blog-messages.md index 7ed6b329bfd..86ad9bcbaf3 100644 --- a/release-team/role-handbooks/communications/templates/feature-blog-messages.md +++ b/release-team/role-handbooks/communications/templates/feature-blog-messages.md @@ -99,7 +99,7 @@ This is a message to send Feature Blog authors in their Feature Blog PR if they ``` Hi @xx 👋 -- this is YOURNAME (@your_github_id) from the vX.yy Communications Team! -Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: **<> WEEKDAY, DAY MONTH**. By this deadline, your blog should be complete with all content finalized for review. If you are still working on it, please prioritize finishing it by the deadline mentioned above. +Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: **<> WEEKDAY, DAY MONTH**. We ask you to have the blog in non-draft state, and all write-up to be complete, so that we can start the blog review from SIG Docs Blog team. If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you! ```