Skip to content

Commit 0be23c9

Browse files
committed
[docs] Create upgrade notes for
1 parent 24f21f6 commit 0be23c9

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

website/community/how-to-release/creating-a-fluss-release.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,8 @@ Create a release branch from the `main` branch in the cloned Fluss repository. T
113113

114114
```bash
115115
$ git checkout main
116-
$ git checkout -b release-${RELEASE_VERSION_SHORT}
117-
$ git push origin release-${RELEASE_VERSION_SHORT}
116+
$ git checkout -b release-${SHORT_RELEASE_VERSION}
117+
$ git push origin release-${SHORT_RELEASE_VERSION}
118118
```
119119

120120
Update the version in the Helm Chart in:
@@ -128,8 +128,8 @@ For example, if you are releaseing a major version `0.8.0`, you should replace a
128128
And commit/push the version bump:
129129

130130
```bash
131-
$ git commit -m "Bump version to x.y.z" docker/helm/Chart.yaml docker/helm/values.yaml docker/helm/README.md
132-
$ git push origin release-${RELEASE_VERSION_SHORT}
131+
$ git commit -m "[helm] Bump version to ${RELEASE_VERSION}" docker/helm/Chart.yaml docker/helm/values.yaml docker/helm/README.md
132+
$ git push origin release-${SHORT_RELEASE_VERSION}
133133
```
134134

135135
</TabItem>
@@ -153,7 +153,7 @@ And commit/push the version bump:
153153

154154
```bash
155155
$ git commit -m "Bump version to x.y.z" docker/helm/Chart.yaml docker/helm/values.yaml docker/helm/README.md
156-
$ git push origin release-${RELEASE_VERSION_SHORT}
156+
$ git push origin release-${SHORT_RELEASE_VERSION}
157157
```
158158

159159
</TabItem>
@@ -171,7 +171,7 @@ After creating the release branch, you should bump the version of the main branc
171171
```bash
172172
$ cd tools
173173
tools $ git checkout main
174-
tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$NEXT_VERSION releasing/update_branch_version.sh
174+
tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
175175
tools $ git push origin main
176176
```
177177

@@ -191,7 +191,7 @@ Additionally, for the upgrade notes page of the version currently being released
191191
Commit the documentation changes, and push to the official repository.
192192

193193
```bash
194-
$ git commit -m "[docs] Create upgrade notes for $NEXT_VERSION"
194+
$ git commit -m "[docs] Create upgrade notes for $NEXT_SHORT_VERSION" .
195195
$ git push origin main
196196
```
197197
</TabItem>
@@ -254,7 +254,7 @@ TAG="v${RELEASE_VERSION}-rc${RC_NUM}"
254254
Now, checkout from the release branch, and create a release candidate local branch:
255255

256256
```bash
257-
$ git checkout release-${RELEASE_VERSION_SHORT}
257+
$ git checkout release-${SHORT_RELEASE_VERSION}
258258
$ cd tools
259259
tools $ RELEASE_CANDIDATE=$RC_NUM RELEASE_VERSION=$RELEASE_VERSION releasing/create_release_branch.sh
260260
```

website/docs/maintenance/operations/upgrade-notes-0.8.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Upgrade Notes
3-
sidebar_position: 3
3+
sidebar_class_name: hidden
44
---
55

66
# Upgrade Notes from v0.7 to v0.8

website/docs/maintenance/operations/upgrade-notes-0.9.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Upgrade Notes
3-
sidebar_class_name: hidden
3+
sidebar_position: 3
44
---
55

66
# Upgrade Notes from v0.8 to v0.9

0 commit comments

Comments
 (0)