commit | d5174b1f44b7d9cb919d4975b4d437041273c09c | [log] [tgz] |
---|---|---|
author | Alex Petrov <oleksandr.petrov@gmail.com> | Thu Dec 03 13:59:24 2020 +0100 |
committer | Alex Petrov <oleksandr.petrov@gmail.com> | Thu Dec 03 13:59:24 2020 +0100 |
tree | a7f3a6b79b329da55b6b16673aa7b6078977f0fa | |
parent | 2b7e2850c2bd2299810e10821aa10fa41bd0e511 [diff] |
[maven-release-plugin] prepare for next development iteration
Shared API package for in-JVM distributed tests.
mvn versions:set -DnewVersion=0.0.2-`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