commit | 1ba6ef93d0721741b5f6d6d72cba3da03fe78438 | [log] [tgz] |
---|---|---|
author | Dinesh Joshi <djoshi@apache.org> | Wed Aug 16 13:55:40 2023 -0700 |
committer | Dinesh Joshi <djoshi@apache.org> | Wed Aug 16 13:55:40 2023 -0700 |
tree | ae184f6b2bf1153bb1d7fab1ec5a864b1711f8ba | |
parent | f3a3b982227602ec0752a5d0d4d780dc62ac3f6d [diff] |
[maven-release-plugin] prepare release 0.0.16
Shared API package for in-JVM distributed tests.
mvn versions:set -DnewVersion=`xpath -n -q -e '/project/version/text()' pom.xml | awk -F- '{print $1}'`-`git rev-parse --short HEAD`-SNAPSHOT mvn deploy
mvn release:clean CURRENT=0.0.CURRENT NEXT_DEV=0.0.NEXT mvn -DreleaseVersion=$CURRENT -Dtag=$CURRENT -DdevelopmentVersion=$NEXT_DEV-SNAPSHOT release:prepare mvn release:perform
Close staging repository: https://repository.apache.org/#stagingRepositories
Issue a vote on developers mailing list. Add your GPG key signature, release SHA, and staged artifacts to release information.
Parent pom location: https://maven.apache.org/pom/asf/ Maven distribution docs: http://www.apache.org/dev/publishing-maven-artifacts.html Creating a new reposotory: https://selfserve.apache.org/
To generate key, run:
gpg --full-gen-key
To be able to sign releases with this key, make sure your key is:
gpg --list-sigs "<YOUR_NAME>" gpg --verbose --send-keys --keyserver hkps://hkps.pool.sks-keyservers.net <YOUR_KEY_IDENTIFIER_HERE> # to test if it has worked: gpg --verbose --recv-keys --keyserver hkps://hkps.pool.sks-keyservers.net <YOUR_KEY_IDENTIFIER_HERE>
svn co --depth files https://dist.apache.org/repos/dist/release/cassandra/ release (gpg --list-sigs "<YOUR_NAME>" && gpg --armor --export "<YOUR_NAME>") >> KEYS svn commit KEYS -m "Add <YOUR NAME>'s key for releases" # or ask some PMC to do this for you by opening CASSANDRA jira, like this one: https://issues.apache.org/jira/browse/CASSANDRA-15534