> Chunwei, did `prepareVote` fail when you were making rc0? If so, I think
those nexus repos were a byproduct and can be dropped.
Yes. it indeed failed before success.
Best,
Chunwei
On Fri, Jul 24, 2020 at 12:44 PM Francis Chuang
wrote:
> Actually, I am not sure why there are 6 repositories
I dry run it, it will remove all the artifacts before 1.24.0. I think that is
not Calcite's policy. At least it should keep 1.23.0.
On 2020/07/24 04:40:50, Francis Chuang wrote:
> orgapachecalcite-1096 is closed and released, so that's fine. The other
> open ones are for rcs that did not
Actually, I am not sure why there are 6 repositories for 1.22.0 on nexus
with 3 being closed and released.
Chunwei, did `prepareVote` fail when you were making rc0? If so, I think
those nexus repos were a byproduct and can be dropped.
Francis
On 24/07/2020 2:40 pm, Francis Chuang wrote:
Can everyone please not commit to master branch for a moment?
The release manager hasn't open the master branch yet.
On 2020/07/24 04:38:07, Haisheng Yuan wrote:
> Skipped the step of releaseRepository too.
> Now finished release.
>
> There are several closed or open repos in
>
orgapachecalcite-1096 is closed and released, so that's fine. The other
open ones are for rcs that did not pass, so I don't think they should be
closed and released.
There are currently 3 calcite releases in the release folder:
https://dist.apache.org/repos/dist/release/calcite/
We should
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 wrote:
> I skipped the step, but now have this error:
>
I skipped the step, but now have this error:
~/calcite ❯❯❯ ./gradlew publishDist -Prc=0 -Pasf -x publishSvnDist
> Configure project :
Building Apache Calcite 1.24.0
> Task :releaseRepository
Initialized stagingRepositoryId orgapachecalcite-1096
for repository nexus
POST request failed. 500:
How can I skip this step?
~/calcite ❯❯❯ ./gradlew publishDist -Prc=0 -Pasf
> Configure project :
Building Apache Calcite 1.24.0
> Task :publishSvnDist FAILED
Listing SVN folders [dev/calcite/apache-calcite-1.24.0-rc0] at
https://dist.apache.org/repos/dist
Build calcite FAILURE reason:
I will help push the artifacts.
On 2020/07/24 03:04:05, Francis Chuang 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:
> >
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
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
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
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 details
> Configure project :
Building Apache Calcite 1.24.0
> Task :publishSvnDist
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
14 matches
Mail list logo
