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 MichaelBusch
Date Thu, 24 Jan 2008 01:18:15 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 MichaelBusch:
http://wiki.apache.org/lucene-java/ReleaseTodo

------------------------------------------------------------------------------
  https://svn.apache.org/repos/asf/lucene/java/tags/release-X.Y.Z -m "Lucene Java X.Y.Z release."
  }}}
     1. If this is your first release, add your key to the KEYS file. The KEYS file is located
in Subversion at [WWW] https://svn.apache.org/repos/asf/lucene/java/dist and copy it to the
release directory. Make sure you commit your change.
+    1. See [http://jakarta.apache.org/site/convert-to-mirror.html?Step-By-Step Guide To Distributing
Existing Releases Through The ASF Mirrors] and the links that are there.
     1. Copy the files to the release directory {{{people.apache.org:/www/www.apache.org/dist/lucene/java}}}
     1. Copy the Maven artifacts to the distribution directory (follow the existing directory
structure), to have them pushed to the central Maven repositories:   {{{people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/lucene}}}
+    1. Update nightly.sh in SVN (via Hudson's account on zones is the easiest way) with the
new version for publishing the Maven artifacts.  Ask Grant or Michael B. for help, as they
have zones accounts
     1. Wait 24 hours to give the mirrors a chance to get the new release.
+ 
+ = Announcing =
+ 
     1. Update the website (See http://wiki.apache.org/solr/Website_Update_HOWTO for Solr's
guide to using Forrest) {{{
    ssh www.apache.org
    cd /www/lucene.apache.org/java
@@ -85, +90 @@

  
    mv lucene-X.Y.Z/docs/api api
  }}}
-    1. Update nightly.sh in SVN (via Hudson's account on zones is the easiest way) with the
new version for publishing the Maven artifacts.  Ask Grant or Michael B. for help, as they
have zones accounts
  
- = Announcing =
- 
-    1. See [http://jakarta.apache.org/site/convert-to-mirror.html?Step-By-Step Guide To Distributing
Existing Releases Through The ASF Mirrors] and the links that are there.
     1. Announce the release on [http://www.freshmeat.net]
+    1. Announce the release on the development, user and announce mailinglists. 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).
     1. Go to JIRA and find all issues that were fixed in the release you just made, whose
Status is Resolved, and do a bulk change to close all of these issues.  Uncheck the box that
says "send an email for these changes".

Mime
View raw message