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 HossMan
Date Tue, 07 Feb 2012 21:01:22 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 HossMan:

  = Release Workflow =
   1. Check out the branch with: {{{svn co}}}
-  1. Add an entry for the new version in the doap.rdf file, stored under docs/doap.rdf in
the unversioned site (see
   1. If the release is < 3.0, ensure "ant test-core" passes in a 1.4 Java environment.
Important: Do two tests: Compile & test with Java 1.4, but also compile with Java 5 and
only run tests with 1.4. This ensures, that the artifacts are really working with Java 1.4
(see the comment [[|]]
for explanation).
   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? Does the demo application work correctly? Does Test2BTerms pass?
@@ -91, +90 @@

   1. Wait 24 hours to give the mirrors a chance to get the new release.
  = Pushing website changes & Announcing =
+ /!\ needs heavy updating to reflect new CMS based website /!\
+ /!\ BEGIN this info is all out of date /!\
   1. Checkout the top-level Lucene website from
Add a new item under "News", in index.xml. Run "forrest site", confirm all looks good, then
recursively copy build/site/* to publish/*, then commit the changes. Then copy publish/* to
/www/* on Be sure to change the group and attributes
of the copied files: {{{cd /www/; chgrp -R lucene * ; chmod -R ug+w,o-w
   1. Checkout the unversioned Lucene java website from
Add a new item under "Lucene News", in index.xml. Add a new entry for this release into both
tabs.xml and site.xml. Run "forrest site", confirm all looks good, and recursively copy build/site/*
to docs/*, then commit the changes. Copy docs/* to /www/ on
Make sure .htaccess is copied!
   1. Copy the release specific docs from the binary release package to
@@ -101, +106 @@

    rmdir lucene-X.Y.Z
   1. Make sure the group ownership on the site is 'lucene' by calling {{{chgrp -R lucene
/www/}}}. Also make files group writable and others read-only by calling
{{{chmod -R ug+w,o-w /www/}}}.
+ /!\ END this info is all out of date /!\
+  1. update the core & solr doap.rdf files to reflect the new versions using the Apache
+     *
+     *
   1. Wait for these changes to appear on Apache's main webserver (
before doing the next steps (see for details on
how the site is mirrored to Apache's main web servers). Once they appear, verify all links
are correct in your changes!
   1. Add the new version to Wikipedia (english and maybe your own language)
   1. Announce the release on , ,
and mailing lists. A draft should be sent to the development list first
to clarify any possible issues in the announcement.  Make sure the announcement has a brief
blurb at the top saying what Lucene is (it will save you several snarky comments in reply.)
Mails to the announce list should be sent from an email address and contain a
signature.  Release announcements can be shared/edited in

View raw message