vlsi commented on issue #104: CALCITE-3158: Avatica: migrate build system to 
Gradle
URL: https://github.com/apache/calcite-avatica/pull/104#issuecomment-551295251
 
 
   > Speed was also quite good
   
   Just in case, you can add `-m` (== `--dry-run`) and it will print the list 
of tasks it is about to execute.
   
   For instance, `prepareVote` does not execute tests.
   
   >I have only tried the prepareVote task so far. Are there any other ones I 
should try?
   
   `./gradlew publishDist -Prc=0` to publish the candidate.
   
   > This is so that the release manager will not need to mess around with 
command line arguments and properties
   
   Most of the properties are a one-time configuration for the machine.
   For instance, `signing.gnupg.keyName`, `asfCommitterId`, `asf*Username` 
could be saved to the properties in the home directory.
   `asfTest*` could be saved as well.
   
   I do not think it would be great to type the same `asfCommitterId` again and 
again in the "interactive" mode.
   
   What if the script takes certain properties from 
`$HOME/.gradle/gradle.properties`?
   Then it would reduce the set of properties to type.
   
   > the interactive aspects in the script to select the GPG key and set the 
appropriate command
   
   It is sad that "release with Docker" requires lots of commands to type.
   To release "without Docker" one needs "Java, Git, SVN" (ps. SVN seems to be 
missing in the docs).
   The release itself is 2 short commands, and the script would suggest the 
missing properties automatically.
   
   The release "with Docker" requires significant preparations (gpg install, 
copy keyring, etc, etc).
   It could probably make sense to add a Dockerfile with gpg installed so one 
could just run a simple command and get suitable environment for the release / 
verification.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to