Skip to content

Commit d26096c

Browse files
authored
Merge pull request #18173 from jimangel/fix-release-info
fixing information about dev contrib
2 parents 8ac20ba + 00b106a commit d26096c

File tree

2 files changed

+46
-4
lines changed

2 files changed

+46
-4
lines changed

content/en/docs/contribute/new-content/new-features.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ card:
1414
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).
1515

1616
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
1818
`kubernetes/website` repository, and someone on the SIG Docs team provides
1919
editorial feedback or edits the draft directly. This section covers the branching
2020
conventions and process used during a release by both groups.
@@ -96,9 +96,9 @@ deadlines.
9696
### Open a placeholder PR
9797

9898
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
100100
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
102102
assign the PR to the relevant milestone. This alerts the docs person managing
103103
this release that the feature docs are coming.
104104

@@ -121,7 +121,7 @@ content is not received, the feature may be removed from the milestone.
121121

122122
### All PRs reviewed and ready to merge
123123

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
125125
docs person managing the release to get it in by the deadline. If your feature needs
126126
documentation and the docs are not ready, the feature may be removed from the
127127
milestone.

layouts/shortcodes/skew.html

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
<!-- capture version from first argument in "skew" -->
2+
{{- $version := .Get 0 -}}
3+
4+
<!-- strip "v" from latest verison -->
5+
{{- $latestVersion := site.Params.latest -}}
6+
{{- $latestVersion := (replace $latestVersion "v" "") -}}
7+
8+
<!-- splits a string x.Xy into substrings separated by a "." delimiter -->
9+
{{- $versionArray := split $latestVersion "." -}}
10+
11+
<!-- capture minorVersion ("Xy") in a variable -->
12+
{{- $minorVersion := int (index $versionArray 1) -}}
13+
14+
<!-- increment latest 1 minor number for "nextMinorVerison" -->
15+
{{- $nextMinorVersion := add $minorVersion 1 -}}
16+
17+
<!-- subtract latest 1 minor number for "prevMinorVerison" -->
18+
{{- $prevMinorVersion := sub $minorVersion 1 -}}
19+
20+
<!-- output nextMinorVersion based on captured arg -->
21+
{{- if eq $version "nextMinorVersion" -}}
22+
{{- $nextMinorVersion := printf "%s.%d" (index $versionArray 0) $nextMinorVersion -}}
23+
{{- $nextMinorVersion -}}
24+
{{- end -}}
25+
26+
<!-- output latestVersion based on captured arg -->
27+
{{- if eq $version "latestVersion" -}}
28+
{{- $latestVersion -}}
29+
{{- end -}}
30+
31+
<!-- output prevMinorVersion based on captured arg -->
32+
{{- if eq $version "prevMinorVersion" -}}
33+
{{- $prevMinorVersion := printf "%s.%d" (index $versionArray 0) $prevMinorVersion -}}
34+
{{- $prevMinorVersion -}}
35+
{{- end -}}
36+
37+
<!--
38+
example shortcode use:
39+
- skew nextMinorVersion
40+
- skew latestVersion
41+
- skew prevMinorVersion
42+
-->

0 commit comments

Comments
 (0)