lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "HowToRelease" by GrantIngersoll
Date Mon, 26 Oct 2009 21:32:56 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "HowToRelease" page has been changed by GrantIngersoll.
http://wiki.apache.org/solr/HowToRelease?action=diff&rev1=45&rev2=46

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

    1. Create a new distribution directory: {{{people.apache.org:/www/www.apache.org/dist/lucene/solr/X.Y}}}
   1. Check out the branch with:           {{{svn co https://svn.apache.org/repos/asf/lucene/solr/branches/branch-X.Y
\}}}
    . '''Note:''' at the moment releases need to be done on a unix box or in a cygwin environment
with unix linefeeds, because fixcrlf is only done on the sources in the zip artifact
-  1. Update the version numbers in common-build.xml on the trunk:
+  1. Update the version numbers in common-build.xml on the branch:
    * {{{specversion}}} should be set to `X.Y.M.${dateversion}`, where X.Y.M is the release
being made.
+   * {{{version}}} should be set to `X.Y.M`.
+   * {{{maven_version}}} should be the same as {{{version}}} for release but set to X.Y-SNAPSHOT
for non-release.
+  1. Update the version numbers in common-build.xml on trunk:
+   * {{{specversion}}} should be set to `X.Y.M.${dateversion}`, where X.Y.M is the '''next'''
release to be made, assuming an incremental minor.
    * {{{version}}} should be set to `X.Y.N-dev`, where N is one greater than the release
being made.
-   * {{{maven_version}}} should be the same as {{{version}}} for release but set to X.Y-SNAPSHOT
for non-release.
-  1. Update the version numbers in common-build.xml on the newly created branh:
-   * {{{specversion}}} should be set to `X.Y.M`, where X.Y.M is the release being made.
-   * {{{version}}} should be set to `X.Y.N`, where N is one greater than the release being
made.
    * {{{maven_version}}} should be the same as {{{version}}}
   1. commit the changes to both trunk and branch
   1. On the branch, compile the code and run unit tests.
-   . {{{ant clean test}}}
+   . {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M clean test}}}
   1. Regenerate the "site" docs per [[Website_Update_HOWTO]] so the documentation included
with this release will reflect the correct version number (at the moment, this is specific
to the tutorial)
   1. Commit the build.xml and documentation changes from the previous few steps.
   1. Build the release (see the later step on prepare-release also once you are experienced
with doing the next steps by hand)
-   . {{{ant package}}}
+   . {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M package}}}
   1. Check that release tgz/zip files looks ok - e.g. uncompress them, run example, work
through the steps of the tutorial, ensure that the javadocs are readable, etc...
   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).
    * {{{gpg --armor --output dist/apache-solr-X.Y.M.tgz.asc --detach-sig dist/apache-solr-X.Y.M.tgz}}}

Mime
View raw message