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 <jus...@classsoftware.com> 于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
