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 21:40:22 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=95&rev2=96

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

   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 }}}[-Dgpg.exe=/path/to/gpg -Dgpg.key=YourKeyID
-Dgpg.passphrase=YourPassPhrase{{{] clean dist-all generate-maven-artifacts sign-artifacts
 //Items in [] are optional}}}
+  1. Build the release artifacts: {{{ant -Dversion=X.Y.Z }}}[-Dgpg.exe=/path/to/gpg -Dgpg.key=YourKeyID
-Dgpg.passphrase=YourPassPhrase{{{] clean dist-all generate-maven-artifacts sign-artifacts
 //Items in [] are optional}}}
   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. ant copy-to-stage to move the artifacts up to the staging area
+  1. ant -Dversion=X.Y.Z copy-to-stage to move the artifacts up to the staging area (see
the build target for all the options for securly copying the artifacts up)
  
  = Publishing =
  Once [[http://www.apache.org/foundation/voting.html#ReleaseVotes|three PMC members have
voted for a release]], it may be published.

Mime
View raw message