Author: tallison
Date: Tue Sep 10 14:12:19 2013
New Revision: 1521497
URL: http://svn.apache.org/r1521497
Log:
small changes to release-guide.txt based on experience with releasing 3.10-beta2
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=1521497&r1=1521496&r2=1521497&view=diff
==============================================================================
--- poi/site/src/documentation/release-guide.txt (original)
+++ poi/site/src/documentation/release-guide.txt Tue Sep 10 14:12:19 2013
@@ -24,7 +24,10 @@
(I) Prerequisites
1. You should read the <a href="http://apache.org/dev/release.html";>Apache
Release FAQ</a>
- 2. You must have shell access to people.apache.org
+ 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>.
+ 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.
More info can be found here: <a
href="http://www.apache.org/dev/release-signing.html";>http://www.apache.org/dev/release-signing.html</a>
4. You must have <a href="java.sun.com">JDK 1.5</a>
@@ -33,12 +36,15 @@
* <a href="www.gnupg.org">gnupg</a>
* <a href="www.openssl.org">openssl</a>
For Windows users, install Cygwin and make sure you have the above
utilities
- 6. The POI build system requires two components to perform a build
+ 6a. The POI build system requires two components to perform a build
* <a href="ant.apache.org">Ant</a>
* <a href="http://forrest.apache.org/";>Forrest</a>.
POI 3.0.2 and 3.1 were built using Ant 1.6.2 and Forrest 0.5
Currently, Forrest needs to be 0.5.1, Ant 1.7+ should be fine
+ 6b. To deploy with Maven, you should have the latest stable Maven 2.x.
+ POI 3.10-beta2 was deployed with Maven 2.2.1.
+
7. Before building, you should run the "rat-check" build task, which
uses <a href="http://incubator.apache.org/rat/";>Apache Rat</a>
to check the source tree for files lacking license headers. Files
@@ -83,8 +89,8 @@ https://svn.apache.org/repos/asf/poi/tag
where $TAG is the release tag, for example, REL_3_1_BETA1
- 5. On trunk, update "version.id" to be the next version, and remove
- the version pinning on the documentation external definition.
+ 5. On trunk, update "version.id" to be the next version in status.xml,
+ and remove the version pinning on the documentation external definition.
6. Checkout the tagged version
{code}
@@ -127,12 +133,15 @@ svn co https://dist.apache.org/repos/dis
mkdir 3.8-RC3/
svn add 3.8-RC3
+(may need --force as in:
+svn add 3.8-RC3 --force
+)
then add .gz and .zip packages along with checksums.
binaries should be in ./bin, sources in ./src sub-directories
8c. commit
-After commit the files should be acessible at
https://dist.apache.org/repos/dist/dev/poi/3.8-RC2/
+After commit the files should be accessible at
https://dist.apache.org/repos/dist/dev/poi/3.8-RC2/
(III) After the vote:
@@ -163,20 +172,18 @@ cd build/dist
./mvn-deploy.sh
{code}
-2. Make sure that the files are owned by the unix group apcvs and that they
are writable by this group.
-
-3. Wait for the distributions to appear on your favourite mirror
+2. Wait for the distributions to appear on your favourite mirror
-4. Edit the website homepage and list the new release there. If a full release,
+3. Edit the website homepage and list the new release there. If a full release,
remove older full releases and all beta releases. If a beta release, keep
the last full release, and replace any other beta releases
-5. Edit the website download page, and list the new release there. This should
+4. Edit the website download page, and list the new release there. This should
reference the checksums, so take care when updating
-6. Commit the site changes to svn, and publish live
+5. Commit the site changes to svn, and publish live
-7. test maven
+6. test maven
create a simple project and make sure the release artifacts are accessible by
maven:
{code}
@@ -204,12 +211,15 @@ mvn compile
You should see [INFO] BUILD SUCCESSFUL in the end.
-8. Don't forget to upload the latest version of the site and javadocs
+Before the package is fully replicated, you may get a BUILD SUCCESSFUL, but
you'll also receive a
+warning that the .jar can't be downloaded. Wait until you get BUILD
SUCCESSFUL and no warnings.
+
+7. Don't forget to upload the latest version of the site and javadocs
-9. Send announcements:
+8. Send announcements:
- to poi-user and poi-dev lists
- to [email protected], [email protected]
Note, announcements should be sent from your @apache.org e-mail address.
-10. add a new project version in Bugzilla
+9. Add a new project version in Bugzilla
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
