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:24:46 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.
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=85&rev2=86

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

  svn cp https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_X_Y/lucene/src/
backwards/src/
  ant test-backwards
  }}}
-  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.
   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:
@@ -63, +62 @@

  
  = 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
-  1. Guestimate the release date and update CHANGES.txt on the branch and commit it
   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}}}

Mime
View raw message