You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/contribute/new-content/new-features.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,8 @@ deadlines.
98
98
1. Open a pull request against the
99
99
`dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small
100
100
commit that you will amend later.
101
-
2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).
101
+
2. Edit the pull request description to include links to [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes)
102
+
PR(s) and [kubernetes/enhancements](https://github.com/kubernetes/enhancements) issue(s).
102
103
3. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
103
104
assign the PR to the relevant milestone. This alerts the docs person managing
104
105
this release that the feature docs are coming.
@@ -115,7 +116,9 @@ When ready, populate your placeholder PR with feature documentation.
115
116
116
117
Do your best to describe your feature and how to use it. If you need help structuring your documentation, ask in the `#sig-docs` slack channel.
117
118
118
-
When you complete your content, the documentation person assigned to your feature reviews it. Use their suggestions to get the content to a release ready state.
119
+
When you complete your content, the documentation person assigned to your feature reviews it.
120
+
To ensure technical accuracy, the content may also require a technical review from corresponding SIG(s).
121
+
Use their suggestions to get the content to a release ready state.
119
122
120
123
If your feature needs documentation and the first draft
121
124
content is not received, the feature may be removed from the milestone.
0 commit comments