lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by MikeMcCandless
Date Mon, 02 Mar 2009 19:13:07 GMT
Dear Wiki user,

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

The following page has been changed by MikeMcCandless:

     1. Build the code and javadocs, and run the unit tests: ant clean javadocs test
     1. Examine the results. Did it build without errors? Were there Javadoc warnings? Did
the tests succeed?
     1. In preparation for the next step, download the Maven ant tasks JAR (eg maven-ant-tasks-2.0.9.jar)
from, and add into your CLASSPATH, or add "-lib XXX.jar"
to the ant command in the next step
+    1. Remove contrib/benchmark/{work,temp} if present
     1. Package the release with a command like: {{{ant -Dversion=2.3.0-rc1 -Dspec.version=2.3.0
clean dist dist-src generate-maven-artifacts}}}.  Make sure it finishes successfully.
     1. Generate Changes.html by running {{{ant changes-to-html}}}, then open build/docs/changes/Changes.html
with a browser and confirm it looks right.
     1. Create a staging area on your public Apache website {{{
@@ -56, +57 @@

     1. Guestimate the release date and update CHANGES.txt on the branch and commit it
     1. Update src/site/changes/ (in setup_release_dates) with the date, and
commit it to trunk and branch
     1. Verify that "svnversion" reports a single revision with no modified changes
+    1. Remove contrib/benchmark/{work,temp} if present
     1. Build the release artifacts: {{{ant -Dversion=2.3.0 clean dist dist-src generate-maven-artifacts}}}
     1. Sanity check the overall size of each artifact. EG, compare to the last release.
     1. Make sure that for each release file an md5 checksum file exists.

View raw message