Update new feature doc to add a step to include necessary links
parent
91ae1f7e19
commit
2c31d6a19d
|
@ -14,12 +14,11 @@
|
|||
Use the default base branch, “master”, if you're documenting existing
|
||||
features in the English localization.
|
||||
|
||||
If you're working on a different localization (not English), or you
|
||||
are documenting a feature that will be part of a future release, see
|
||||
If you're working on a different localization (not English), see
|
||||
https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use
|
||||
for advice.
|
||||
|
||||
Use the next release branch, "dev-x.xx", if you're documenting a feature for
|
||||
a release. If applicable, please also include links to k/k and k/enhancement.
|
||||
If you're documenting a feature that will be part of a future release, see
|
||||
https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.
|
||||
|
||||
-->
|
||||
|
|
|
@ -98,7 +98,8 @@ deadlines.
|
|||
1. Open a pull request against the
|
||||
`dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small
|
||||
commit that you will amend later.
|
||||
2. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
|
||||
2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).
|
||||
3. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
|
||||
assign the PR to the relevant milestone. This alerts the docs person managing
|
||||
this release that the feature docs are coming.
|
||||
|
||||
|
|
Loading…
Reference in New Issue