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 GrantIngersoll
Date Fri, 25 Mar 2011 16:33:19 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 GrantIngersoll.
The comment on this change is: minor updates to clean up, more coming.
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=86&rev2=87

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

- This page is to help a Lucene/Solr committer create a new release (you need committer rights
for some of the steps to create an official release). It does not reflect official release
policy - many of the items may be optional, or may be modified as necessary. 
+ This page is to help a Lucene/Solr committer create a new release (you need committer rights
for some of the steps to create an official release). It does not reflect official release
policy - many of the items may be optional, or may be modified as necessary.
  
  = Release Process =
  With the release of Lucene Java 2.2.0 a new release process was established. Prior to every
major release a feature freeze phase takes place for about 1-2 weeks. At the beginning of
the feature freeze the trunk is branched and no commits other than serious bug fixes, documentation
or build updates are permitted. This period of time should be used for extensive testing,
documentation improvements and for cleaning up old JIRA issues.
  
+ = Prerequisites =
+  1. Download the Maven ant tasks JAR (maven-ant-tasks-2.1.1.jar) from http://maven.apache.org/ant-tasks/download.html,
 and add into your $HOME/.ant/lib/ directory, or $ANT_HOME/lib/  directory, or $CLASSPATH,
or add "-lib XXX.jar" to the ant command in  the next step.
+ 
  = Planning =
- On dev@lucene.apache.org, decide on
+ On dev@lucene.apache.org , decide on
  
   1. which JIRA issues shall be committed before a release is made; set the appropriate "Fix
Version" in JIRA for these issues
   1. the date for branching the trunk and the start of the feature freeze phase
@@ -42, +45 @@

   1. If the release is < 3.0, ensure "ant test-core" passes in a 1.4 Java environment.
Important: Do two tests: Compile & test with Java 1.4, but also compile with Java 5 and
only run tests with 1.4. This ensures, that the artifacts are really working with Java 1.4
(see the comment [[https://issues.apache.org/jira/browse/LUCENE-2285?focusedCommentId=12839224&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12839224|https://issues.apache.org/jira/browse/LUCENE-2285?focusedCommentId=12839224&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12839224]]
for explanation).
   1. Build the code and javadocs, and run the unit tests: ant clean javadocs test
   1. Examine the results. Did it build without errors? Were there Javadoc warnings? Did the
tests succeed? Does the demo application work correctly? Does Test2BTerms pass?
-  1. In preparation for the next step, download the Maven ant tasks JAR (maven-ant-tasks-2.1.1.jar)
from http://maven.apache.org/ant-tasks/download.html, and add into your $HOME/.ant/lib/ directory,
or $ANT_HOME/lib/ directory, or $CLASSPATH, or add "-lib XXX.jar" to the ant command in the
next step.
   1. Remove contrib/benchmark/{work,temp} if present
-  1. Package the release with a command like: {{{ant -Dversion=2.3.0-rc1 -Dspec.version=2.3.0
clean dist dist-src generate-maven-artifacts}}}. Make sure it finishes successfully.
+  1. Package the release with a command like: {{{ant -Dversion=2.3.0-rc1 -Dspec.version=2.3.0
clean dist-all generate-maven-artifacts}}}. Make sure it finishes successfully.
   1. Generate Changes.html by running {{{ant changes-to-html}}}, then open build/docs/changes/Changes.html
with a browser and confirm it looks right.
   1. Create a staging area on your public Apache website
   {{{
@@ -64, +66 @@

   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
   1. Verify that "svnversion" reports a single revision with no modified changes
   1. Remove contrib/benchmark/{work,temp} if present
-  1. Build the release artifacts: {{{ant -Dversion=2.3.0 clean dist dist-src generate-maven-artifacts}}}
+  1. Build the release artifacts: {{{ant -Dversion=2.3.0 clean dist-all generate-maven-artifacts}}}
   1. Sanity check the overall size of each artifact. EG, compare to the last release.
   1. Make sure that for each release file an md5 checksum file exists.
   1. Sign the release (see [[http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step|Step-By-Step
Guide to Mirroring Releases]] for more information). Also sign all Maven release artifacts.

Mime
View raw message