diff --git a/openjdk-latest.spec b/openjdk-latest.spec
index 29491a1ed771e8ce3697569ded71fa7da02a6475..0b01d72fd839c310e5a5945af963811ef92a5dbd 100644
--- a/openjdk-latest.spec
+++ b/openjdk-latest.spec
@@ -154,7 +154,7 @@
 %global majorver 21
 # Used via new version scheme. JDK 19 was
 # GA'ed in March 2022 => 22.3
-%global vendor_version_string 22.3
+%global vendor_version_string BiSheng
 %global securityver 0
 # buildjdkver is usually same as %%{majorver},
 # but in time of bootstrap of next jdk, it is majorver-1,
@@ -894,7 +894,7 @@ Name:    java-latest-%{origin}
 Version: %{newjavaver}.%{buildver}
 # This package needs `.rolling` as part of Release so as to not conflict on install with
 # java-X-openjdk. I.e. when latest rolling release is also an LTS release packaged as
-Release: %{?eaprefix}%{rpmrelease}%{?extraver}.rolling
+Release: 1
 
 # java-1.5.0-ibm from jpackage.org set Epoch to 1 for unknown reasons
 # and this change was brought into RHEL-4. java-1.5.0-ibm packages
@@ -1346,7 +1346,7 @@ bash ../configure \
     --with-version-pre=\"${EA_DESIGNATOR}\" \
     --with-version-opt=%{lts_designator} \
     --with-vendor-version-string="%{vendor_version_string}" \
-    --with-vendor-name="openEuler Community" \
+    --with-vendor-name="BiSheng" \
     --with-vendor-url="https://openeuler.org/" \
     --with-vendor-bug-url="%{bug_url}" \
     --with-vendor-vm-bug-url="%{bug_url}" \
@@ -1773,7 +1773,11 @@ cjc.mainProgram(arg)
 
 
 %changelog
+* Mon Nov 27 2023 kuenking111 <wangkun49@huawei.com> - 1:21.0.0.35-1
+- Change vendor name to BiSheng
+
 * Sat Oct 7 2023 kuenking111 <wangkun49@huawei.com> - 1:21.0.0.35-0-rolling
+- upgrade to jdk21+35
 
 * Mon Aug 07 2023 misaka00251 <liuxin@iscas.ac.cn> - 1:20.0.2.9-1-rolling
 - Add riscv64 to jit_arches