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 MikeMcCandless
Date Sat, 11 Oct 2008 13:09:41 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

The comment on the change is:
Fix announcing step for copying from the 3 website sources.

------------------------------------------------------------------------------
  
  = Announcing =
  
-    1. Update the website (See http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite)
{{{
+    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 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. Copy the release specific docs to people.apache.org: {{{
-   ssh www.apache.org
+   ssh people.apache.org
-   cd /www/lucene.apache.org/java
- 
-   mkdir MAJOR_MINOR_BUILD directory where MAJOR, MINOR, BUILD correspond to the version,
e.g. 2_3_0 contains the 2.3.0 release site.  See the existing structure in the directory if
you have any questions
- 
-   Copy the release docs dir into this dir (make sure you do a recursive copy)
- 
-   Add a new link to the "Documentation" section of the main website (site.xml and tabs.xml
in https://svn.apache.org/repos/asf/lucene/java/site/src/documentation/content/xdocs) similar
to the existing links.  This change will be automatically sync'd with the main website via
the nightly build.
- }}}
-    1. Update the javadocs on the website under the directory version you have created above.
This is done by unpacking it from the release that you've just made, moving it into place.
{{{
-   ssh www.apache.org
- 
-   cd /www/lucene.apache.org/java/MAJOR_MINOR_BUILD (see above)
- 
-   tar xzf lucene-X.Y.Z.tar.gz lucene-X.Y.Z/docs/api
+   tar xzf lucene-X.Y.Z lucene-X.Y.Z/docs
+   mv lucene-X.Y.Z/docs /www/lucene.apache.org/java/X_Y_Z
+   rmdir lucene-X.Y.Z}}}
+    1. Wait for these changes to appear on Apache's main webserver (http://lucene.apache.org)
before doing the next steps.  Once they appear, verify all links are correct in your changes!
- 
-   mv lucene-X.Y.Z/docs/api api
- }}}
- 
     1. Announce the release on [http://www.freshmeat.net]
-    1. Add a new item under "News" to the top-level web site (commit changes to https://svn.apache.org/repos/asf/lucene/site)
-    1. Add a new item under "Lucene News" to the Lucene Java web site (commit changes to
https://svn.apache.org/repos/asf/lucene/java/site)
     1. Announce the release on java-dev@lucene.apache.org, java-user@lucene.apache.org and
announce@apache.org mailing lists. A draft should be sent to the development list first to
clarify any possible issues in the announcement. Mails to the announce list should be sent
from an @apache.org email address and contain a signature.
     1. Ensure the latest Lucene Jar + MD5 sum file have been pushed to http://repo1.maven.org/maven2/org/apache/lucene/
by deploying the distribution to http://people.apache.org/repo/m2-ibiblio-rsync-repository/
(that is minotaur.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository).  From
there it will be pushed to the central Maven repositories (both Maven 1 and Maven 2) automatically
in a few hours. Contact repository@apache.org if there's some problem.
     1. Go to the JIRA "Manage Versions" Administration page (http://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310110)
and click Release for the version you just released.  Also add a new (unreleased) version
for the next release on the trunk (for a major release) or branch (for a minor release).

Mime
View raw message