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 UweSchindler
Date Wed, 17 Mar 2010 14:08:07 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 UweSchindler.
The comment on this change is: New backwards compatibility todo after release of a new major
version..
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=76&rev2=77

--------------------------------------------------

  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). Also update the LUCENE_MAIN_VERSION in src/java/org/apache/lucene/util/Constants.java.
Also add the new enum constant into src/java/org/apache/lucene/util/Version.java. Update src/test/org/apache/lucene/util/LuceneTestCaseJ4.java
to use the current version.
-  1. Create a new backwards branch for trunk based on the branch already created for the
release. Link this branch in common-build.xml.
+  1. Prepare the backwards-compatibility tests in trunk (only if a new major release was
started and you created the branch before):
+  {{{
+ svn rm backwards/src/
+ svn cp https://svn.apache.org/repos/asf/lucene/java/branches/lucene_X_Y/src/ backwards/src/
+ ant test-backwards
+ }}}
+ Commit changes
   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 the branch, fix the same files, rebuild the website and commit.

Mime
View raw message