wuchong commented on code in PR #2672:
URL: https://github.com/apache/fluss/pull/2672#discussion_r2802089974
##########
website/community/how-to-release/creating-a-fluss-release.mdx:
##########
@@ -195,30 +180,44 @@ Additionally, for the upgrade notes page of the version
currently being released
Commit the documentation changes, and push to the official repository.
```bash
-$ git commit -m "[docs] Create upgrade notes for $NEXT_SHORT_VERSION" .
+$ git commit -m "[docs] Create upgrade notes for $SHORT_NEXT_VERSION" .
$ git push origin main
```
**(3) Add version item in fluss-versions.json**
-Next, add a new version item for the current release version in the
`website/fluss-versions.json` file on the `main` branch. The new version item
should have the following fields and values (releasing `0.8.0` as an example):
+Next, add a new version item for the next release version in the
`website/fluss-versions.json` file on the `main` branch. The new version item
should have the following fields and values (current releasing `0.9.0`, next
release `0.10.0` as an example):
```json
{
- "versionName": "version-0.8",
- "fullVersion": "0.8.0-incubating",
- "shortVersion": "0.8",
- "dockerVersion": "0.8.0-incubating-rc1",
+ "versionName": "next",
+ "fullVersion": "0.10-SNAPSHOT",
+ "shortVersion": "0.10",
+ "dockerVersion": "0.10-SNAPSHOT",
+ "paimonVersion": "1.3.1",
+ "paimonVersionShort": "1.3",
"released": false
}
```
-Additionally, update the `fullVersion`, `shortVersion`, and `dockerVersion`
fields for the `next` version entry to reflect the next release version.
+Additionally, update the `fullVersion`, `shortVersion`, and `dockerVersion`
fields for the `current` version entry to reflect the current release version.
+
+```json
+{
+ "versionName": "version-0.9",
+ "fullVersion": "0.8.0-incubating",
+ "shortVersion": "0.8",
+ "dockerVersion": "0.8.0-incubating",
+ "paimonVersion": "1.3.1",
+ "paimonVersionShort": "1.3",
+ "released": false
+ }
+```
Commit the documentation changes, and push to the official repository.
```bash
-$ git commit -m "[docs] Add version item for $RELEASE_VERSION in
fluss-versions.json
+$ git commit -m "[docs] Add version item for $RELEASE_VERSION"
fluss-versions.json
Review Comment:
The original intention is
```suggestion
$ git commit -m "[docs] Add version item for $RELEASE_VERSION in
fluss-versions.json"
```
##########
website/community/how-to-release/release-manager-preparation.md:
##########
@@ -121,7 +121,7 @@ sub rsa4096 2025-08-07 [E]
Determine your Apache GPG Key and Key ID, as follows:
```bash
-gpg --list-keys
+gpg --list-keys --keyid-format short
Review Comment:
OK. Both returns the same result for me. But I'm using `gnupg2` mentioned in
https://fluss.apache.org/community/how-to-release/release-manager-preparation/#generate-a-gpg-key
##########
website/community/how-to-release/creating-a-fluss-release.mdx:
##########
@@ -115,21 +115,6 @@ Create a release branch from the `main` branch in the
cloned Fluss repository. T
$ git checkout main
$ git checkout -b release-${SHORT_RELEASE_VERSION}
$ git push origin release-${SHORT_RELEASE_VERSION}
-```
-
-Update the version in the Helm Chart in:
Review Comment:
I think we still need this if releasing a bugfix version. Could you still
keep it, but just describe this is only need to check the version and may need
to update for minor bugfix version release?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
