Besides, just check the binary release tar package, there includes several versions of gravitino jars, which is not correct.
``` -rw-r--r--@ 1 jerryshao staff 272K Apr 1 17:41 gravitino-api-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 272K Apr 1 17:41 gravitino-api-0.9.0-incubating-SNAPSHOT.jar -rw-r--r--@ 1 jerryshao staff 272K Apr 1 17:41 gravitino-api-0.9.0.jar -rw-r--r--@ 1 jerryshao staff 34K Apr 1 17:41 gravitino-catalog-common-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 379K Apr 1 17:41 gravitino-common-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 379K Apr 1 17:41 gravitino-common-0.9.0-incubating-SNAPSHOT.jar -rw-r--r--@ 1 jerryshao staff 379K Apr 1 17:41 gravitino-common-0.9.0.jar -rw-r--r--@ 1 jerryshao staff 964K Apr 1 17:41 gravitino-core-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 1.0M Apr 1 17:41 gravitino-core-0.9.0-incubating-SNAPSHOT.jar -rw-r--r--@ 1 jerryshao staff 964K Apr 1 17:41 gravitino-core-0.9.0.jar -rw-r--r--@ 1 jerryshao staff 142K Apr 1 17:41 gravitino-server-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 135K Apr 1 17:41 gravitino-server-0.9.0-incubating-SNAPSHOT.jar -rw-r--r--@ 1 jerryshao staff 142K Apr 1 17:41 gravitino-server-0.9.0.jar -rw-r--r--@ 1 jerryshao staff 65K Apr 1 17:41 gravitino-server-common-0.8.1.jar -rw-r--r--@ 1 jerryshao staff 65K Apr 1 17:41 gravitino-server-common-0.9.0-incubating-SNAPSHOT.jar -rw-r--r--@ 1 jerryshao staff 65K Apr 1 17:41 gravitino-server-common-0.9.0.jar ``` Saisai Shao <[email protected]> 于2025年4月2日周三 21:41写道： > Some artifacts like Maven staging repo, python rc library should also be > verified during the release, not after the release. Otherwise, we don't > know if the release is working or not. > > AFAIK, most of the projects will ship staging artifacts during the release > vote, not after the release vote. > > The script covers all the steps. We'd better fix the script before doing > the release. > > > Justin Mclean <[email protected]> 于2025年4月2日周三 21:02写道： > >> Hi, >> >> > Did you also publish to maven repository, Pypi repository and Dockerhub >> for rc1? >> >> No as there is no requirement to do so and they can be published after >> the release is voted on. In fact, publishing unreleased artifacts to 3rd >> parties platforms is not really in line ASF policy as they should not be >> made available to the general public. [1][2][3] >> >> > Also, which tag is the RC1 tag, can you please send out the link? >> >> The release scripts contained an error, which meant the wrong branch got >> tagged. I’ll fix this, but you can see the release is one commit ahead of >> branch-0.8. >> >> Kind Regards, >> Justin >> >> 1. https://www.apache.org/legal/release-policy.html#compiled-packages >> 2. https://www.apache.org/legal/release-policy.html#release-distribution >> 3. https://www.apache.org/legal/release-policy.html#what > >
