svn commit: r1769487 - /poi/site/src/documentation/release-guide.txt

[on...@apache.org]

Author: onealj
Date: Sun Nov 13 11:16:27 2016
New Revision: 1769487

URL: http://svn.apache.org/viewvc?rev=1769487&view=rev
Log:
update release guide

Modified:
    poi/site/src/documentation/release-guide.txt

Modified: poi/site/src/documentation/release-guide.txt
URL: http://svn.apache.org/viewvc/poi/site/src/documentation/release-guide.txt?rev=1769487&r1=1769486&r2=1769487&view=diff
==============================================================================
--- poi/site/src/documentation/release-guide.txt (original)
+++ poi/site/src/documentation/release-guide.txt Sun Nov 13 11:16:27 2016
@@ -35,8 +35,7 @@
    2b. You must be a member of the committee group
    3. Release manager must have their public key appended to the KEYS file checked in to SVN and the key published on one of the public key servers.
       More info can be found here: <a href="https://www.apache.org/dev/release-signing.html">https://www.apache.org/dev/release-signing.html</a>
-   4. You must have the Java JDK 1.6 installed and active (don't use newer
-      ones for building the release)
+   4. You must have both Java JDK 1.6 and Java JDK 1.7+ installed and active.
    5. You must have the following utilities installed on your local machine and available in your path:
           * <a href="www.openssh.com">ssh</a>
           * <a href="www.gnupg.org">gnupg</a>
@@ -71,7 +70,7 @@
         <server>
             <!-- used for signing the releases -->
             <id>poi-signing</id>
-            <username>keyid</username>
+            <username>keyid (key fingerprint, no spaces)</username>
             <passphrase>password</passphrase>
             <privateKey>.../.gnupg/secring.gpg</privateKey>
         </server>
@@ -95,8 +94,10 @@
       out will cause the executable bit to be set for them on filesystems
       which support it. The flag can be removed in batch using
 
+{code}
 $ svn pd 'svn:executable' $(find -name .svn -prune -or -type f ! -name \*.sh \
  -print0 | xargs -0 svn pg 'svn:executable' | cut -d ' ' -f 1)
+{code}
 
    9. Before building, ensure that the year in the NOTICE file is correct,
       and review any new or updated dependencies to ensure that if they
@@ -108,10 +109,14 @@ $ svn pd 'svn:executable' $(find -name .
       latest ones in svn:
       https://dist.apache.org/repos/dist/dev/poi/KEYS
       https://dist.apache.org/repos/dist/release/poi/KEYS
+      Dist is a regular svn repo that can be checked out and committed to.
       To upload to dist: https://www.apache.org/dev/release-distribution
 
 
 (II) Making release artefacts
+  This is mostly automated with a sequence of 3 release-prep ant targets.
+  Run these commands from a clean checkout of https://svn.apache.org/repos/asf/poi/trunk
+
   1. The following command will update the documentation and create/download the tag (needs a Java7+ environment)
      using your Apache credentials stored in ~/.m2/settings.xml.
      {code}
@@ -119,14 +124,14 @@ $ svn pd 'svn:executable' $(find -name .
      ant -Dversion.id=3.15 release-prep1 (final release)
      {code}
 
-  2. Compile the dist (needs a JDK6 environment)
+  2. Compile the dist (needs a JDK6 environment, sudo update-alternatives --config java)
      {code}
      ant release-prep2
      {code}
 
   3. Upload to the nexus repo and to the svn release candidate repo  (needs a Java7+ environment)
      The nexus repo is located at https://repository.apache.org/
-     The release candidate repo is located at https://dist.apache.org/repos/dist/dev/poi/(3.15-beta1-RC1)
+     The release candidate repo is located at https://dist.apache.org/repos/dist/dev/poi/(3.15-beta2-RC1)
      {code}
      ant -Dversion.id=3.15-beta2 -Drelease.rc=RC1 release-prep3
      {code}



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@poi.apache.org
For additional commands, e-mail: commits-help@poi.apache.org