whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix branch names in “Start Contributing” (#19493)

Browse Source 
* Replaced shortcodes with hard-coded values 1.17

* Updated with shortcode as per PR reveiew

* Update with proper shortcode after rebase
This commit is contained in:
Sujay Pillai
2020-03-09 01:23:34 +08:00
committed by GitHub
parent e7a84f9bc2
commit ead3e36150
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/contribute/start.md
+3 -3
View File
@@ -209,7 +209,7 @@ to base your work on. Use these guidelines to make the decision:
- Some localization teams work with a series of long-lived branches, and - Some localization teams work with a series of long-lived branches, and
periodically merge these to `master`. This kind of branch has a name like periodically merge these to `master`. This kind of branch has a name like
dev-\<version>-\<language code>.\<team milestone>; for example: dev-\<version>-\<language code>.\<team milestone>; for example:
`dev-{{< release-branch >}}-ja.1`. `dev-{{< latest-semver >}}-ja.1`
- If you're writing or updating documentation for a feature change release, - If you're writing or updating documentation for a feature change release,
then you need to know the major and minor version of Kubernetes that then you need to know the major and minor version of Kubernetes that
the change will first appear in. the change will first appear in.
@@ -217,8 +217,8 @@ to base your work on. Use these guidelines to make the decision:
to beta in the next minor version, you need to know what the next minor to beta in the next minor version, you need to know what the next minor
version number is. version number is.
- Find the release branch named for that version. For example, features that - Find the release branch named for that version. For example, features that
changed in the v{{< release-branch >}} release got documented in the branch changed in the {{< latest-version >}} release got documented in the branch
named `dev-{{< release-branch >}}`. named `dev-{{< latest-semver >}}`.
If you're still not sure which branch to choose, ask in `#sig-docs` on Slack or If you're still not sure which branch to choose, ask in `#sig-docs` on Slack or
attend a weekly SIG Docs meeting to get clarity. attend a weekly SIG Docs meeting to get clarity.