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 GrantIngersoll
Date Fri, 25 Mar 2011 18:22:06 GMT
Dear Wiki user,

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

The "ReleaseTodo" page has been changed by GrantIngersoll.
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=91&rev2=92

--------------------------------------------------

   1. Examine the results. Did it build without errors? Were there Javadoc warnings? Did the
tests succeed? Does the demo application work correctly? Does Test2BTerms pass?
   1. Remove contrib/benchmark/{work,temp} if present
   1. Build as defined below in the "Building the Release Artifacts" section.
-  1. Create a staging area on your public Apache website
-  {{{
-    ssh people.apache.org
-    mkdir public_html/staging-area
- }}}
-  1. Copy the release candidate and Changes.html to the staging area and announce on dev@
and java-user@ that it is available for testing. Make sure your directory permissions disallow
writing ({{{chmod -R a-w public_html/staging-area/*}}}, after copying).
-  {{{
-    ssh people.apache.org
-    mkdir public_html/staging-area/rc1
-    scp -r dist people.apache.org:public_html/staging-area/luceneX.Yrc1
-    scp -r build/docs/changes people.apache.org:public_html/staging-area/luceneX.Ychanges
- }}}
   1. If during the feature freeze phase bug fixes are committed to the X.Y branch then build
another release candidate and announce on dev@ and java-user@ that everyone should use the
new RC for testing.
   1. Call a release vote on java-dev and cc general@lucene.apache.org .
  

Mime
View raw message