# To Do checklist with Sig-doc Bi weekly meeting 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](https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/communications/README.md#release-milestone-activities) for a list of recommended activities for this week in the release cycle. ## Communication status for Docs and Release Team - 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 ### Guide to build a new blog - [Information about how create a new blog in Kubernetes](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/#technical-considerations-for-submitting-a-blog-post). - See this sample feature blog: [Add blog for non-graceful node shutdown](https://github.com/kubernetes/website/pull/41914)