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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ card:
14
14
Each major Kubernetes release introduces new features that require documentation. New releases also bring updates to existing features and documentation (such as upgrading a feature from alpha to beta).
15
15
16
16
Generally, the SIG responsible for a feature submits draft documentation of the
17
-
feature as a pull request to the appropriate release branch of the
17
+
feature as a pull request to the appropriate development branch of the
18
18
`kubernetes/website` repository, and someone on the SIG Docs team provides
19
19
editorial feedback or edits the draft directly. This section covers the branching
20
20
conventions and process used during a release by both groups.
@@ -96,9 +96,9 @@ deadlines.
96
96
### Open a placeholder PR
97
97
98
98
1. Open a pull request against the
99
-
`release-X.Y` branch in the `kubernetes/website` repository, with a small
99
+
`dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small
100
100
commit that you will amend later.
101
-
2. Use the Prow command `/milestone X.Y` to
101
+
2. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
102
102
assign the PR to the relevant milestone. This alerts the docs person managing
103
103
this release that the feature docs are coming.
104
104
@@ -121,7 +121,7 @@ content is not received, the feature may be removed from the milestone.
121
121
122
122
### All PRs reviewed and ready to merge
123
123
124
-
If your PR has not yet been merged into the `release-X.Y` branch by the release deadline, work with the
124
+
If your PR has not yet been merged into the `dev-{{< skew nextMinorVersion >}}` branch by the release deadline, work with the
125
125
docs person managing the release to get it in by the deadline. If your feature needs
126
126
documentation and the docs are not ready, the feature may be removed from the
0 commit comments