You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@poi.apache.org by on...@apache.org on 2016/11/09 08:47:11 UTC
svn commit: r1768871 - /poi/site/src/documentation/release-guide.txt
Author: onealj
Date: Wed Nov 9 08:47:11 2016
New Revision: 1768871
URL: http://svn.apache.org/viewvc?rev=1768871&view=rev
Log:
add details for first-timers to 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=1768871&r1=1768870&r2=1768871&view=diff
==============================================================================
--- poi/site/src/documentation/release-guide.txt (original)
+++ poi/site/src/documentation/release-guide.txt Wed Nov 9 08:47:11 2016
@@ -26,9 +26,14 @@
1. You should read the <a href="https://www.apache.org/dev/release.html">Apache Release FAQ</a>
2a. You must have shell access to people.apache.org; and you should
have key-based authentication set up
- (e.g. <a href="http://www.linuxproblem.org/art_9.html">how to</a>.
+ 1. Generate ssh key with ssh-keygen -t rsa -b 4096
+ (e.g. <a href="http://www.linuxproblem.org/art_9.html">how to</a>.)
+ 2. Add contents of id_rsa.pub to SSH Key (authorized_keys) line on https://id.apache.org/
+ 3. ssh -v username@people.apache.org
+ Verify authenticity of host: https://www.apache.org/dev/machines
+ 4. Only sftp access is necessary
2b. You must be a member of the committee group
- 3. Release manager must have his public key appended to the KEYS file checked in to SVN and the key published on one of the public key servers.
+ 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)
@@ -40,7 +45,7 @@
6a. The POI build system requires two components to perform a build
* <a href="https://ant.apache.org">Ant</a>
* <a href="https://forrest.apache.org/">Forrest</a>.
- Currently, Forrest needs to be 0.5.1, Ant 1.8+ should be fine
+ Currently, Forrest needs to be 0.5.x (prefer 0.5.1), Ant 1.8+ should be fine
Make sure FORREST_HOME is set.
6b. To deploy with Maven, you should have the latest stable Maven 2.x.
@@ -64,7 +69,7 @@
<password>apache-passwd</password>
</server>
<server>
- <!-- used for singing the releases -->
+ <!-- used for signing the releases -->
<id>poi-signing</id>
<username>keyid</username>
<passphrase>password</passphrase>
@@ -99,10 +104,11 @@ $ svn pd 'svn:executable' $(find -name .
10. Ensure that the changelog is up to date
- 11. Ensure that the KEYs files in the dist areas are up-to-date with the
+ 11. Ensure that the KEYS files in the dist areas are up-to-date with the
latest ones in svn:
https://dist.apache.org/repos/dist/dev/poi/KEYS
https://dist.apache.org/repos/dist/release/poi/KEYS
+ To upload to dist: https://www.apache.org/dev/release-distribution
(II) Making release artefacts
@@ -142,7 +148,7 @@ find . -name "*.asc" -exec gpg --no-secm
1. The release manager should call the vote
2. Include the URL of the release artifacts
- 3. Include the time for the vote to run
+ 3. Include the time for the vote to run (3 day minimum, can be longer)
4. Provide guidance on what needs to be checked
5. Complete a tally, and send a result once the time has passed
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@poi.apache.org
For additional commands, e-mail: commits-help@poi.apache.org