Logo image size is recommended as maximum 2160px
How many blogs to publish by day?
The current handbook states:
The first feature blog typically goes out on release day alongside or shortly after the release blog, and then are published one-at-a-time, typically at a rate of two to three posts weekly
Priyanka top major themes: https://hackmd.io/@TJDQWIMdSjynqWWmnlbCTg/ryG4hiHHp#Kubernetes-129–-Enhancements
In all the communication to @kubernetes/sig-docs-blog-owners
@kubernetes/sig-docs-blog-owners: Publication Order Nro:2
@kubernetes/sig-docs-blog-owners: Blog scheduled: Dec 14th, Publication Order Nro:2
(What I think) end users really care about:
is it on by default?
if not, can I opt in just through the API or something?
is this deprecated and I have to take some action just to keep things working?
Everything that's not on by default is a lower priority, even if we'd love to get more real world testing.
Same question as above: should we use "stable" or "generally available"?
Hi
@Kirtana Ashok
, how are you? Here from the Communications team for the 1.29 Release :slightly_smiling_face: , I know you have opted out of a feature blog, but could you help us with the description of the main features for KEP 4216, so we can include it in the 1.29 Release blog? We need a paragraph of text. This is the WIP/Draft PR for the Release blog.
Hi @Kirtana Ashok, how are you? Here from the Communications team for the 1.29 Release :slightly_smiling_face: , We are writing the release blog, could you help us to build a paragraph highlighting the major changes in sig-node
related to the notes discussion 1.29.
Hi @mrunal, how are you?, Carol here from the Communications team for the 1.29 Release :slightly_smiling_face: . We are writing the release blog, could you help us to build a paragraph highlighting the major changes in sig-auth
related to the notes discussion 1.29. cc: @Sergey Kanzhelev @liggitt @pacoxu
Schedule the 1.29 release Live Webinar: the live webinar on 12/15 at 9amPT (TBC)
Schedule interview for the release lead: for Dec 4-6 days. (TBC)
Choose the 2-3 top themes and the draft blog.
Please, remember to give the status in the sig-docs every two weeks.
1.29 Board here
1.29 Release Meeting Notes here
1.29 Calendar here
Blog Publication board here
Major themes 1.29 Discussion here
Rey Lejano checklist to Docs: https://github.com/kubernetes/sig-release/pull/2350/files
1.29 retrospective: https://docs.google.com/document/d/1ka-Mc33aakUB7EsvWvKBGc6uK2im9GH5ozRc5ppwMZI/edit#heading=h.ukbaidczvy3r
we expected the blogs ready to review, 1 week before the release
You want the webinar to run sometime within the two weeks immediately after the release. On that email, cc the release-comms alias, the release lead, and the enhancements lead.
the release-comms alias: release-comms@kubernetes.io
the release lead: Priyanka Saggu
the enhancements lead:
Nina Polshakova
3-4 weeks after the release is fine too, I aimed for right after our blogs were finished publishing which ended up being just over two weeks past the release.
Schedule press and analyst pre-briefings and interviews for the release lead with CNCF by emailing pr@cncf.io
Release Week |
Milestones |
Activities |
Status |
Team Member |
1 | Start of release cycle Sep 06, 2023 |
|
Green | Carol Valencia |
2 | Sep 13, 2023 |
|
Green | Carol Valencia |
3 | Production Readiness Freeze Sep 19, 2023 (sig-docs)- Sep 20, 2023 |
|
Green | Hosam Kamel |
4 | Enhancements Freeze (Status Sep 27) |
|
Green | Carol Valencia |
5 |
|
Green | Kristin Martin | |
6 |
|
Yellow | Abigail McCarthy | |
7 |
|
Green | Carol | |
8 |
|
Yellow | Kristin | |
9 |
|
XXX | Abbie | |
10 |
|
XXX | XXX | |
11 | Feature blog freeze |
|
Yellow | Kristin Martin |
12 | Code Freeze |
|
XXX | Abigail McCarthy |
13 |
|
XXX | XXX | |
14 | Feature Blogs ready to review |
|
XXX | Kristin Martin |
15 | Release Week |
|
XXX | Abigail McCarthy |
16 | Release retrospective |
|
XXX | XXX |
Carol | Abigail | James | Kristin | Hosam | |
---|---|---|---|---|---|
sig-network | sig-node | sig-apps | sig-storage | sig-api-machinery | |
sig-windows | sig-k8s-infra | sig-multicluster | sig-instrumentation | sig scalability | |
sig-security | sig cluster lifecycle | sig auth | sig scheduling | sig autoscaling | |
sig cloud provider |
Go to the channel, in this case sig-cloud-provider, introduce yourself and ask about the feature blogs or deprecations, removals.
Docs deadline — PRs ready for review Docs Lead Tuesday 14th November 2023
Sample messages: KEP-2395, KEP-4004
Work in progress KEP PR messsage. DO NOT USE
Hi [issue assignee(s)] 👋, I'm a v1.29 Communication Release Team [shadow/lead] just checking in. Are you planning on writing a blog for this change?
If you are, you will need to open a PR against the main branch in the kubernetes/website repo. This PR can be just a placeholder for now and you can fill in the content later. The deadline for blog placeholder PRs will be on Thursday 19th October 2023. (Note: A placeholder PR for a blog is separate from a placeholder PR for docs updates you may need to make for this change)
For more information on writing a blog, please see the blog contribution page. Let me know if you have any questions, thanks!
Reminder: When in doubt about the status, its ok to report the status as yellow/red. This will alert the other release teams and stakeholders that something needs their attention, and they can help you determine the best status level and create a path forward as needed.
Review the Comms Release Milestones for a list of recommended activities for this week in the release cycle.
How many feature blogs are there for the release?
How many feature blogs are ready to review?
How many blogs are awaiting reviews from the Technical SIG Lead?
How many blogs are awaiting editorial reviews?
Any problems getting a SIG to respond to messages from the comms team?
Any problems or concerns about outstanding blogs?
Do you have any questions or need help with anything?
The PRs feature blogs and blog release Branch is against the main branch - [By confirm] -Integration Branch with the dev-1.29 ?
un hold 20 PR
unsheduled: –->
blogs will be published
If I need to track a KEP that is not in the board?
Talk with the Enhancement Lead and the Release Lead to see the next steps. Maybe it could be added by the normal process (label:"lead-opted-in") or you can add manually to the board.
What is the process to opt in?
Does the author need to submit a placeholder doc PR to the website repo? What is the deadline?
Collate the major themes of the release, including but not limited to:
More details here
search deprecation and removal and see what KEPs have the deprecation section of the readme filled out:
https://github.com/aramase/enhancements/blob/cc018e12db30ceb194f7fdc5e5061c23d081a0c7/keps/sig-auth/3331-structured-authentication-configuration/README.md#deprecation
Deprecations: https://github.com/orgs/kubernetes/projects/161/views/1?filterQuery=type%3ADeprecation
Major changes: https://github.com/orgs/kubernetes/projects/161/views/1?filterQuery=type%3A"Major+Change"
This is the older "Feature blog tracking sheet" for new entries and use the
Assigment tab
sheet to assign and track status throughout the cycle (for example.