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 Wed, 01 Oct 2008 11:30:56 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:
Include contrib/CHANGES.txt

------------------------------------------------------------------------------
  https://svn.apache.org/repos/asf/lucene/java/branches/lucene_X_Y -m "Starting Lucene X.Y
branch."
  }}}
     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 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. 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. 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.
        * Documentation patches, build patches and serious bug fixes may be committed to the
branch. However, you should submit *all* patches you want to commit to Jira first to give
others the chance to review and possibly vote against the patch. Keep in mind that it is our
main intention to keep the branch as stable as possible.
@@ -62, +62 @@

     1. Add an entry for the new version in the doap file for projects.apache.org (docs/doap.rdf)
     1. Tag the release: {{{
  svn copy https://svn.apache.org/repos/asf/lucene/java/branches/lucene_X_Y \
- https://svn.apache.org/repos/asf/lucene/java/tags/release-X.Y.Z -m "Lucene Java X.Y.Z release."
+ https://svn.apache.org/repos/asf/lucene/java/tags/lucene_X_Y_Z -m "Lucene Java X.Y.Z release."
  }}}
-    1. If this is a new branch (eg you are releasing 2.4.0), after tagging, commit a new
"unreleased" section at the top of CHANGES.txt onto the branch
+    1. If this is a new branch (ie you are releasing X.Y.0), after tagging, commit a new
"unreleased" section at the top of CHANGES.txt and contrib/CHANGES.txt onto the branch
     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 KEYS file, and the non-Maven release artifacts to the dist directory {{{people.apache.org:/www/www.apache.org/dist/lucene/java}}},
and remove the old files

Mime
View raw message