commit | b4482d8f657d6fb70fbc407ef2542d10b9772fc6 | [log] [tgz] |
---|---|---|
author | Alex Petrov <oleksandr.petrov@gmail.com> | Thu Apr 16 12:26:34 2020 +0200 |
committer | Alex Petrov <oleksandr.petrov@gmail.com> | Thu Apr 16 12:26:34 2020 +0200 |
tree | 040a3a0e3c3d0b41b0d5e3bea2d2a18decbc0120 | |
parent | e620eb34b73cb3fd3e3a5eeebcd2f5553922a91c [diff] |
Add information about release process
Shared API package for in-JVM distributed tests.
mvn release:clean mvn 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