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 SteveRowe
Date Fri, 01 Apr 2011 15:11:44 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 SteveRowe.
The comment on this change is: -dev -> -SNAPSHOT; java-dev -> dev@; don't drop -SNAPSHOT
from version in common-build.xml.
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=104&rev2=105

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

  svn copy https://svn.apache.org/repos/asf/lucene/dev/trunk \
  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-dev and the default version in lucene/common-build.xml on the branch to
X.Y (remove the -SNAPSHOT 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/LuceneTestCase.java
to use the current version.
+  1. After branching the new release series, update the default version in lucene/common-build.xml
on trunk to X.Y+1-SNAPSHOT. 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/LuceneTestCase.java
to use the current version.
   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,index.xml} to reference
the X.Y+1-dev version. Rebuild the website (http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite)
and commit.
+  1. On trunk, fix src/site/src/documentation/content/xdocs/{tabs.xml,index.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.
@@ -51, +51 @@

   1. Remove contrib/benchmark/{work,temp} if present
   1. Build as defined below in the "Building the Release Artifacts" section.
   1. If during the feature freeze phase bug fixes are committed to the X.Y branch then build
another release candidate and announce on dev@ and java-user@ that everyone should use the
new RC for testing.
-  1. Call a release vote on java-dev and cc general@lucene.apache.org .
+  1. Call a release vote on dev@ and cc general@lucene.apache.org .
  
  = Building the Release artifacts =
   1. If after the last day of the feature freeze phase no blocking issues are in JIRA with
"Fix Version" X.Y then it's time to build the release artifacts

Mime
View raw message