Update on publishing blogs on features that might have breaking chang…#3007
Update on publishing blogs on features that might have breaking chang…#3007SwathiR03 wants to merge 2 commits into
Conversation
…es in a future release. (Based on 1.36 learnings) * Update on publishing blogs on features that might have breaking changes in a future release. (Based on 1.36 learnings) * Also wanted to throw light on the fact that that there are two contribex channels that can be reached out to - sig-contribex and sig-contribex-comms
k8s-ci-robot
added
needs-kind
k8s-ci-robot
added
sig/release
aibarbetta
left a comment
aibarbetta
left a comment
There was a problem hiding this comment.
Left one suggestion to elaborate this case further
Co-authored-by: Agustina Barbetta <agustina.barbetta@gmail.com>
|
/lgtm |
k8s-ci-robot
added
the
lgtm
dipesh-rawat
left a comment
dipesh-rawat
left a comment
There was a problem hiding this comment.
Thanks for update.
/approve
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dipesh-rawat, SwathiR03 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| The Release Communications team is **NOT** responsible for social posting. [SIG Contributor Experience](https://github.com/kubernetes/community/tree/master/sig-contributor-experience) (SIG Contribex) manages the official Kubernetes social accounts and is responsible for all posts to those accounts. SIG Contribex has created automation around blog posts, so once a blog is published to the Kubernetes website, social posts are created and posted according to SIG Contribex's automation schedule. | ||
|
|
||
| If the Communications team and Release Lead determine a feature or other release communication needs a more detailed communications or calls to action, reach out to with SIG Contributor Experience for help making posts use the `@contributor-comms` tag in the `#sig-contribex` Slack channel. | ||
| If the Communications team and Release Lead determine a feature or other release communication needs a more detailed communications or calls to action, reach out to with SIG Contributor Experience for help making posts use the `@contributor-comms` tag in the `#sig-contribex` or `#sig-contribex-comms` Slack channel. |
There was a problem hiding this comment.
I really like the direction of this, it's been a long-standing goal to have better integration between Comms and Contribex Comms. My only doubt here is the use of "or"... not that I have a great answer, but if I do not know either channels, I'm likely to be confused - should I use both? Just the first? Why?
Perhaps something like "#sig-contribex (the SIG main channel) or #sig-contribex-comms (the Comms subproject channel, more directly responsible for blogging and social media)", although this doesn't answer the hypothetical question I just made...
Perhaps:
"Either channels are adequate: as a guideline, you can start in #sig-contribex and then the conversation might follow up in #sig-contribex-comms".
There was a problem hiding this comment.
The reason why I used this phrasing was because the doc only mentioned the contribex channel, but there are technically two channels to have the conversation in.
5 participants
…es in a future release. (Based on 1.36 learnings)
Update on publishing blogs on features that might have breaking changes in a future release. (Based on 1.36 learnings)
Also wanted to throw light on the fact that that there are two contribex channels that can be reached out to - sig-contribex and sig-contribex-comms(and the contribex meetings cover a lot more depending on the agenda).
What type of PR is this:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer: