Update on publishing blogs on features that might have breaking chang…#3007
Open
SwathiR03 wants to merge 1 commit into
Open
Update on publishing blogs on features that might have breaking chang…#3007SwathiR03 wants to merge 1 commit into
SwathiR03 wants to merge 1 commit 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
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
k8s-ci-robot
added
the
area/release-team
k8s-ci-robot
added
sig/release
aibarbetta
reviewed
May 18, 2026
Member
aibarbetta
left a comment
aibarbetta
left a comment
There was a problem hiding this comment.
Left one suggestion to elaborate this case further
| * features that are considered mandatory by the Release Lead. | ||
|
|
||
| It helps to work closely with the Release Lead and use the respective SIG Slack channels to remind the SIGs about opting in to feature blogs and provide any necessary context to blog authors. | ||
| There have been instances where blogs requiring breaking changes for a future release have to be published. These can be published and linked in the release notes/announcement blog posts without requiring the version number in the name. |
Member
There was a problem hiding this comment.
Suggested change
| There have been instances where blogs requiring breaking changes for a future release have to be published. These can be published and linked in the release notes/announcement blog posts without requiring the version number in the name. | |
| There have been instances where blogs covering breaking changes for a future release have to be published. | |
| There are two options for blogs covering breaking changes. They can be published as a regular feature blog (post-release communication) with the standard front matter. Alternatively, if the blog needs to go out before the release announcement, it can be published without the version prefix in the front matter and then linked in the release notes or announcement blog post. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…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: