[Cassandra Wiki] Update of "HowToPublishReleases" by EricEvans

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "HowToPublishReleases" page has been changed by EricEvans:
https://wiki.apache.org/cassandra/HowToPublishReleases?action=diff&rev1=21&rev2=22

Comment:
some clean up; make more concise

  ## page was renamed from HowToPublishToMavenCentral
  = Publishing Apache Cassandra Releases =
  
- ''TODO: Remove all the TODO:'s. Note TODO's are formatted in italic and contain the name of the person who added them at the end so that you know who to ask if you are unsure of what is in the TODO. The name does not imply that the person is doing the TODO ;-) (Stephen)''
- 
- == Target audience ==
- 
- ''TODO: update this section now that it is not just about deploy to maven central but about making releases in general (Stephen)''
- This guide is targeted at Cassandra Developers (and stephenc at apache) who are the only people with permissions to deploy Cassandra artifacts to the Maven Central Repository.
- 
  == Prerequisites ==
  
+  1. You need permissions to deploy Cassandra artifacts to the Maven Central Repository.
-  1. You need to have a GPG private key set-up and listed in the list of offical keys: http://www.apache.org/dist/cassandra/KEYS
+  1. You need to have a GPG public key listed among those at: http://www.apache.org/dist/cassandra/KEYS
-  1. You have a Subversion 1.5+ client installed and on your shell's path. See http://subversion.apache.org/. (Note: Ideally you would use a Subversion 1.6+ client but the minimum is 1.5+)
-  1. You have JDK 6 installed and on your shell's path.
-  1. If you receive an OutOfMemoryError during the build, make sure to have set the environment variable ANT_OPTS=-Xmx512m
   1. Follow the environment configuration steps outlined at: [[http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env|Publishing Maven Artifacts]]. '''''If you are lazy''''', the short version is that you need to have a minimal {{{~/.m2/settings.xml}}} file which at least defines the following 
    {{{
  <settings>
@@ -36, +27 @@

      <profile>
        <id>apache-release</id>
        <properties>
+ 
          <gpg.keyname><!-- enough of the key id to id it --></gpg.keyname>
  
-         <!-- pick one of the following -->
- 
-         <!-- either you feel comfortable with the passphrase on disk -->
-         <gpg.passphrase><!-- your passphrase for your gpg key goes here--></gpg.passphrase>
- 
-         <!-- or you use an agent-->
+         <!-- Use an agent-->
          <gpg.useagent>true</gpg.useagent>
  
        </properties>
@@ -52, +39 @@

  </settings>
  }}}
   Notes
-   * You must have either {{{<gpg.passphrase>}}} or {{{<gpg.useagent>}}} but not both.
    * The GPG keyname is the {{{sec}}} hex code for the key, e.g. if you had
     {{{
  $ gpg --list-secret-keys