[Lucene-java Wiki] Update of "ReleaseTodo" by JanHoydahl

[Apache Wiki <wi...@apache.org>]

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 JanHoydahl:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=271&rev2=272

Comment:
Remove optional (outdated) step for building the release, after LUCENE-5143

  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. It is recommended to clean your Ivy cache by executing {{{rm -rf ~/.ivy2/cache}}} before building the artifacts. This ensures that all Ivy dependencies are freshly downloaded, so we emulate a user that never used the Lucene build system before (this step ensures downloadability of all artifacts). If you have a ton of stuff in your ivy cache, it's a good idea to move the cache temporarily to another location and restore it after the RC has been built so you wouldn't have to download everything again. This expects you to use ant-1.8.x to build the artifacts. So, ensure that you have ant-1.8.x is installed and that is there in the path when you run the following commands.
-  1. Option 1 (recommended): use {{{dev-tools/scripts/buildAndPushRelease.py}}} to build a release candidate and stage the results locally. Run {{{buildAndPushRelease.py}}} with {{{ --help }}} to learn the available options. Here's an example of what was done for the 6.0.1 release:
+  1. Use {{{dev-tools/scripts/buildAndPushRelease.py}}} to build a release candidate and stage the results locally. Run {{{buildAndPushRelease.py}}} with {{{ --help }}} to learn the available options. Here's an example of what was done for the 6.0.1 release:
    a. Build the release candidate: {{{python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local /tmp/releases/6.0.1 --rc-num 1 --sign <key-id>}}}
    a. Run the smoke test script against the local release candidate: {{{python3 -u dev-tools/scripts/smokeTestRelease.py /tmp/releases/6.0.1/lucene-solr-6.0.1-RC1-rev...}}}
    a. Import the artifacts into SVN: {{{svn -m "Lucene/Solr 6.0.1 RC1" import /tmp/releases/6.0.1/lucene-solr-6.0.1-RC1-rev... https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.0.1-RC1-rev...}}}
    a. If you have cancelled a prior release candidate, remove it from SVN: {{{svn -m "Remove cancelled Lucene/Solr 6.0.1 RC1" rm https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.0.1-RC1-rev...}}}
    a. Don't delete these artifacts from your local workstation as you'll need to publish the maven subdirectories once the RC passes (see below).
-  1. Option 2: manually build a release candidate:
-   a. Verify that {{{svnversion}}} reports a single revision with no modified changes
-   a. Remove {{{lucene/benchmark/{work,temp}/}}} if present
-   a. Build the release artifacts: {{{ant -Dversion=X.Y.Z }}}[{{{-Dgpg.exe=/path/to/gpg -Dgpg.key=YourKeyID -Dgpg.passphrase=YourPassPhrase}}}]{{{ prepare-release}}}  (Items in [] may be optional)
-   a. Sanity check the overall size of each artifact. EG, compare to the last release.
-   a. Make sure that for each release file a sha512 checksum file exists.
-   a. {{{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)
-  Example for 3.1:
-   . {{{
-      PROMPT$ ANT_OPTS="-Xmx256m -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=128M" ant -Dversion=3.1.0 -Dgpg.key=FE045966 prepare-release
-      # Inspect the artifacts
-      PROMPT$ ant -Dversion=3.1.0 -Drc=rc3 -Dscp.user=gsingers copy-to-stage
- }}}
  
  = Initiate a Vote =
   1. If the smoke test passes against the staged artifacts, send an email to the dev mailing list announcing the release candidate. You can use a subject of the form: