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 RobertMuir
Date Wed, 30 May 2012 00:28:37 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 RobertMuir:
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=119&rev2=120

Comment:
add updating of IndexFormatTooOldException, nuke some forresting

  https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_X_Y -m "Starting Lucene/Solr
X.Y branch."
  }}}
   1. After branching the new release series, update the default version in lucene/common-build.xml
on trunk to X.Y+1-SNAPSHOT as well as tests.luceneMatchVersion to X.Y+1. 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-framework/java/org/apache/lucene/util/LuceneTestCase.java to use the current
version.
+  1. If it is a new major version, also update IndexFormatTooOldException to have the correct
minimum version string.
   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/dev/branches/lucene_solr_X_Y/lucene/src/
backwards/src/
  ant test-backwards
  }}}
-  1. On trunk, fix src/site/src/documentation/content/xdocs/tabs.xml to reference the X.Y+1-SNAPSHOT
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 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.

Mime
View raw message