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] Trivial Update of "ReleaseTodo" by MikeMcCandless
Date Tue, 14 Oct 2008 17:47:16 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:
http://wiki.apache.org/lucene-java/ReleaseTodo

------------------------------------------------------------------------------
  }}}
     1. After branching the new release series, update the default version in common-build.xml
on trunk to X.Y+1-dev and the default version in common-build.xml on the branch to X.Y (remove
the -dev suffix).
     1. Update CHANGES.txt and contrib/CHANGES.txt in trunk and the branch. Specify tentative
release date and start a new section for X.Y+1-dev in the trunk's CHANGES.txt.
-    1. On trunk, fix src/site//src/documentation/content/xdocs/{tabs.xml,index.xml} to reference
the X.Y+1-dev version.  Rebuild the website (http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite)
and commit.
+    1. On trunk, fix src/site/src/documentation/content/xdocs/{tabs.xml,index.xml} to reference
the X.Y+1-dev version.  Rebuild the website (http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite)
and commit.
     1. On the branch, fix the same files, rebuild the website and commit.
     1. Send a note to java-dev to inform the committers that the branch has been created
and the feature freeze phase has started. Include Do's and Don'ts for the feature freeze phase:
        * No new features may be committed to the branch.
@@ -79, +79 @@

     1. Wait 24 hours to give the mirrors a chance to get the new release.
  
  = Announcing =
-    1. Checkout the top-level Lucene website from https://svn.apache.org/repos/asf/lucene/site.
 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.  These changes should
be pushed, nightly, to /www/lucene.apache.org, but if you are impatient you can manually copy
them.
+    1. Checkout the top-level Lucene website from https://svn.apache.org/repos/asf/lucene/site.
 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.  These changes should
be pushed, nightly, to /www/lucene.apache.org on people.apache.org, but if you are impatient
you can manually copy them.
-    1. Checkout the Lucene java website from https://svn.apache.org/repos/asf/lucene/java/site.
 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.  These changes should be pushed, nightly,
to /www/lucene.apache.org, but if you are impatient you can manually copy them.
+    1. Checkout the Lucene java website from https://svn.apache.org/repos/asf/lucene/java/site.
 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.  These changes should be pushed, nightly,
to /www/lucene.apache.org/java/docs on people.apache.org, but if you are impatient you can
manually copy them.  Make sure you keep the other files in that directory; specifically at
least .htaccess and doap.rdf.
     1. Copy the release specific docs to people.apache.org: {{{
    ssh people.apache.org
    tar xzf lucene-X.Y.Z lucene-X.Y.Z/docs

Mime
View raw message