You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Vladimir Sitnikov <si...@gmail.com> on 2019/07/22 16:49:12 UTC

[VOTE] Apache Calcite Avatica: Gradle-based release artifacts ready for review

NOTE: This is NOT a vote for releasing Apache Calcite Avatica.

The purpose is mail is to let you know the state of Gradle-based build.
If would be nice if you could review Apache Calcite Avatica 1.16.0-rc1
artifacts.

Note: I have not removed Maven-related files from Git, however the
intention is to completely remove Maven-based build.


Here's an asciinema of the build&release process:
https://asciinema.org/a/258594

Here are my notes:
* Release script does not create Git tag. It should probably create and
push tag before staging the artifacts.
Should it?
Note: Gradle-based script does not need to commit "-SNAPSHOT" vs
"non-snapshot" version changes.

* Release promotion should somehow identify the rc to promote. Any
suggestions?
Should it just search for the latest rc tag? Should it assume for a command
line parameter?

* "committer login" should probably be configurable (currently the script
just prints TBD)

* "preview site" should probably be created (then the script could publish
javadoc/rat preview)
Alternative option is to drop "preview site"-related info from the "draft
vote template".

* We might want to have release-related tasks to "delete stale artifacts
from dist.apache.org"

Below notes are taken from build script output.

------

I have created a build for Apache Calcite Avatica 1.16.0-rc1, release
candidate 1.

The commit to be voted upon:
https://github.com/vlsi/calcite-avatica/commit/5fadc4a2bb49f91778d047a3a20c1d7e6d1fcbc3

Its hash is 5fadc4a2bb49f91778d047a3a20c1d7e6d1fcbc3

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.16.0-rc1

The hashes of the artifacts are as follows:
*apache-calcite-avatica-1.16.0-rc1-src.tar.gz
794e8674539bf0b6eb40111f97b2f6b627be156a992a8b8cd423d55af10e907e86072077697f7cff95af55436dddead9219e6b900e8b4be11c8b9c4ee562f37c
*apache-calcite-avatica-1.16.0-rc1-src.zip
ebf2033261ed79a3a67695d512f48d4b2c19b4c0de53e387c9ca902f74562e0c0c63271875d19620cc005e04730a1d6da6df02cf4548d9088f8d2a01f591daee

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1065/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/vladimirsitnikov.asc
https://www.apache.org/dist/calcite/KEYS

N.B.
To create the jars and test Calcite Avatica: "./gradlew build".

NOTE: This is NOT a vote for releasing Apache Calcite Avatica.

Vladimir

Re: [VOTE] Apache Calcite Avatica: Gradle-based release artifacts ready for review

Posted by Vladimir Sitnikov <si...@gmail.com>.
On the past weekend I've updated release plugins, so most of my notes are
resolved.

TL;DR:
1) ./gradlew prepareVote -Prc=1 -Pasf # build and stage RC1
2) ./gradlew prepareVote -Prc=2 -Pasf # build and stage RC2
2) ./gradlew publishDist -Prc=2 -Pasf # release RC2 as a release

-Prc is mandatory for prepareVote and publishDist tasks.
publishDist performs "svn mv", so there's no need to delete the latest RC
from SVN.

PS. -Pasf stands for "push artifacts to apache.org services like
dist.apache.org / repository.apache.org". By default it pushes artifacts to
local mock servers.

Vladimir