There are currently 3 calcite releases in the release folder: https://dist.apache.org/repos/dist/release/calcite/
We should just keep the latest 2 releases, so I think you can just use svn to remove 1.22.0. There's the `removeStaleArtifacts` command [1], but I have not tested it myself.
Francis[1] https://github.com/vlsi/vlsi-release-plugins/tree/master/plugins/stage-vote-release-plugin#removing-stale-artifacts
On 24/07/2020 2:38 pm, Haisheng Yuan wrote:
Skipped the step of releaseRepository too. Now finished release. There are several closed or open repos in https://repository.apache.org/#stagingRepositories, should I manually release all of them? On 2020/07/24 04:25:43, Haisheng Yuan <hy...@apache.org> wrote:I skipped the step, but now have this error: ~/calcite ❯❯❯ ./gradlew publishDist -Prc=0 -Pasf -x publishSvnDistConfigure project :Building Apache Calcite 1.24.0Task :releaseRepositoryInitialized stagingRepositoryId orgapachecalcite-1096 for repository nexus POST request failed. 500: Server Error, body: [errors:[[id:*, msg:Unhandled: Missing staging repository: orgapachecalcite-1096 ]]]Task :releaseRepository FAILEDBuild calcite FAILURE reason: Execution failed for task ':releaseRepository': io.codearte.gradle.nexus.infra.NexusHttpResponseException: 500: Server Error, body: [errors:[[id:*, msg:Unhandled: Missing staging repository: orgapachecalcite-1096 ]]] at io.codearte.gradle.nexus.infra.SimplifiedHttpJsonRestClient.sendRequestHandlingErrors(SimplifiedHttpJsonRestClient.groovy:52) On 2020/07/24 04:19:14, Haisheng Yuan <hy...@apache.org> wrote:How can I skip this step? ~/calcite ❯❯❯ ./gradlew publishDist -Prc=0 -PasfConfigure project :Building Apache Calcite 1.24.0Task :publishSvnDist FAILEDListing SVN folders [dev/calcite/apache-calcite-1.24.0-rc0] at https://dist.apache.org/repos/dist Build calcite FAILURE reason: Execution failed for task ':publishSvnDist': Unable to list folders [dev/calcite/apache-calcite-1.24.0-rc0] at https://dist.apache.org/repos/dist: svn: warning: W160013: URL 'https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.24.0-rc0' non-existent in revision 40660 svn: E200009: Could not list all targets because some targets don't exist I met an error when executing the command. But the command executed some steps successfully before error out. After I fixed the issue and re-execute the command, now I see this error. Because the folders is already removed from dev directory. On 2020/07/24 04:00:14, Haisheng Yuan <hy...@apache.org> wrote:I will help push the artifacts. On 2020/07/24 03:04:05, Francis Chuang <francischu...@apache.org> wrote:I wonder if this is because only PMCs can push to the SVN repo. If this is the case, I think we need to nominate a PMC member to push the artifacts for you. On 24/07/2020 12:58 pm, Chunwei Lei wrote:Hi, Francis. I already put those settings in ~/.gradle/gradle.properties: $cat ~/.gradle/gradle.properties asfCommitterId=chunwei asfNexusUsername=chunwei asfNexusPassword=xxx asfSvnUsername=chunwei asfSvnPassword=xxx asfGitSourceUsername=chunweilei asfGitSourcePassword=xxx useGpgCmd=true signing.gnupg.useLegacyGpg=true signing.gnupg.keyName=1F1597F99BCE51A1 asfTestSvnPassword=test asfTestSvnUsername=test asfTestGitSourceUsername=test asfTestGitSourcePassword=test asfTestNexusUsername=test asfTestNexusPassword=test Best, Chunwei On Fri, Jul 24, 2020 at 10:46 AM Francis Chuang <francischu...@apache.org> wrote:You need to include your username and password using the -Pasf* flags. Here's how I use those flags to publish an avatica release using docker: https://github.com/apache/calcite-avatica/blob/master/docker.sh#L251 Francis On 24/07/2020 12:43 pm, Chunwei Lei wrote:Hi all, I tried to push the release out to mirrors. But I met an error: $ ./gradlew publishDist -Prc=0 -Pasf Starting a Gradle Daemon, 3 busy and 1 incompatible Daemons could not be reused, use --status for detailsConfigure project :Building Apache Calcite 1.24.0Task :publishSvnDistListing SVN folders [dev/calcite/apache-calcite-1.24.0-rc0] at https://dist.apache.org/repos/dist Executing svnmucc. root=https://dist.apache.org/repos/dist, message=Promoting Apache Calcite calcite-1.24.0-rc0 -> calcite-1.24.0 to release area, commands: mkdir release/calcite/apache-calcite-1.24.0 cp 40574 dev/calcite/apache-calcite-1.24.0-rc0/apache-calcite-1.24.0-src.tar.gz release/calcite/apache-calcite-1.24.0/apache-calcite-1.24.0-src.tar.gz cp 40574dev/calcite/apache-calcite-1.24.0-rc0/apache-calcite-1.24.0-src.tar.gz.ascrelease/calcite/apache-calcite-1.24.0/apache-calcite-1.24.0-src.tar.gz.asccp 40574dev/calcite/apache-calcite-1.24.0-rc0/apache-calcite-1.24.0-src.tar.gz.sha512release/calcite/apache-calcite-1.24.0/apache-calcite-1.24.0-src.tar.gz.sha512rm dev/calcite/apache-calcite-1.24.0-rc0 svnmucc: E175013: Access to '/repos/dist/!svn/txr/40659-yas/release/calcite/apache-calcite-1.24.0' forbiddenTask :publishSvnDist FAILEDBuild calcite FAILURE reason: Execution failed for task ':publishSvnDist': org.gradle.process.internal.ExecException: Process 'command 'svnmucc'' finished with non-zero exit value 1 atorg.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:417)atorg.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)atorg.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:156)atorg.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1147)at com.github.vlsi.gradle.release.SvnmuccTask.mucc(SvnmuccTask.kt:137) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104) Any step I may miss? Best, Chunwei On Fri, Jul 24, 2020 at 12:28 AM Chunwei Lei <chunwei.l...@gmail.com>wrote:Thanks to everyone who has tested the release candidate and given their comments and votes. The tally is as follows. 5 binding +1s: Michael Mior Julian Hyde Haisheng Yuan Francis Chuang Danny Chen 4 non-binding +1s: Enrico Olivelli Ruleben Q L Rui Wang Chunwei Lei 1 binding 0s: Stamatis Zampetakis No -1s. Therefore I am delighted to announce that the proposal to release Apache Calcite 1.24.0 has passed. Thanks everyone. We’ll now roll the release out to the mirrors. The release notes will be updated afterward according to the feedback. Best, Chunwei