Update the docs handbook to include responsibilities posting on Slack #2933
+36
−0
Conversation
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
k8s-ci-robot
added
the
kind/documentation
k8s-ci-robot
added
area/release-team
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sayanchowdhury 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
size/M
Signed-off-by: Sayan Chowdhury <[email protected]>
sayanchowdhury
force-pushed
the
sayan/docs-handbook-slack-distribution
branch
from
908be8c to
c0ad9f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What type of PR is this:
/kind documentation
What this PR does / why we need it:
In the v1.35 release, the Docs team clearly posted tasks and responsibilities in the Slack group, along with assigned owners and reviewers, throughout the release cycle. This greatly helped the team track progress and ensure work was completed on time without unnecessary interference. Documenting this approach will help future teams adopt the same practice.
Which issue(s) this PR fixes:
Special notes for your reviewer:
cc @Urvashi0109