Add information about release process
1 file changed
tree: 040a3a0e3c3d0b41b0d5e3bea2d2a18decbc0120
  1. src/
  2. test/
  3. .gitignore
  4. LICENSE.txt
  5. NOTICE.txt
  6. pom.xml
  7. README.md
README.md

Apache Cassandra in-JVM DTest API

Shared API package for in-JVM distributed tests.

Releasing

  1. Prepare the release:
mvn release:clean
mvn release:prepare
mvn release:perform
  1. Close staging repository: https://repository.apache.org/#stagingRepositories

  2. Issue a vote on developers mailing list. Add your GPG key signature, release SHA, and staged artifacts to release information.

Additional resources:

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/

GPG Key

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>
  • added to KEYS file
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