lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by HossMan
Date Sat, 19 May 2007 01:08:59 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 HossMan:
http://wiki.apache.org/lucene-java/ReleaseTodo

------------------------------------------------------------------------------
  How to make a release:(see also: http://wiki.apache.org/lucene-hadoop/HowToRelease)
   1. If this is the first release in a series (i.e. release X.Y.0), then create a branch
for the series: 		{{{svn copy https://svn.apache.org/repos/asf/lucene/java/trunk \}}} 			{{{https://svn.apache.org/repos/asf/lucene/java/branches/branch-X.Y
-m "Starting Lucene X.Y branch." }}}	
   1. Check out the branch with: 		{{{svn co https://svn.apache.org/repos/asf/lucene/java/branches/branch-X.Y
\}}}
+  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. Build the release with a command like:
+  1. Package the release with a command like:
-    {{{ant -Dversion=1.9-rc1 dist dist-src}}} (The version here should be formatted as in
default.properties.)
+    {{{ant -Dversion=1.9-rc1 clean dist dist-src}}} (The version here should be formatted
as in default.properties.)
   1. Examine the results.  Did it build without errors?  Unpack the release somewhere, examine
the files, run some simple tests.  Do not proceed further until you are confident that this
release is of appropriate quality.
   1. Update the CHANGES.txt file. Check the email archives, and make sure that there is an
entry in this file for every significant CVS commit message.
   1. Commit CHANGES.txt changes and the docs.

Mime
View raw message