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

[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 SteveRowe:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=250&rev2=251

Comment:
After a release, always run addVersion.py and addBackCompatIndexes.py on the release branch

     * Do the following on the release branch, the stable branch, and on the unstable branch:
       * {{{python3 -u dev-tools/scripts/addVersion.py X.Y.Z}}}
       * {{{git add -u .; git commit; git push}}}
-    * Make sure that the backcompat index for the previous release has been added to the release branch.  (Note that this will ordinarily '''not''' have been done if the current release is {{{X.Y.1}}}, i.e. the first bugfix release off the stable branch.)  See the post-release section "Generate Backcompat Indexes" below - remember you'll be generating an index for the '''previous''' release.
+    * Make sure that the backcompat index for the previous release has been added to the release branch.  See the post-release section "Generate Backcompat Indexes" below - remember you'll be generating an index for the '''previous''' release.
    * If a minor release, you'll be adding the '''next''' minor version, not the version being released.  Do the following on the stable branch and on the unstable branch:
     * {{{python3 -u dev-tools/scripts/addVersion.py X.Y+1.0}}}
     * {{{git add -u .; git commit; git push}}}
@@ -315, +315 @@

  
  python3 -u -B dev-tools/scripts/releasedJirasRegex.py 5.5.2 solr/CHANGES.txt 
  }}}
+ == Increment the version on the release branch ==
+ Add the next version after the just-released version on the release branch.
+  * {{{python3 -u dev-tools/scripts/addVersion.py X.Y.Z+1}}}
+  * {{{git add -u .; git commit; git push}}}
  
  == Generate Backcompat Indexes ==
  After each version of Lucene is released, compressed CFS and non-CFS indexes created with the newly released version are added to {{{lucene/backwards-codecs/src/test/org/apache/lucene/index/}}}, for use in testing backward index compatibility via {{{org.apache.lucene.index.TestBackwardsCompatibility}}}, which is also located under the {{{backwards-codecs/}}} module.  These indexes are created via methods on {{{TestBackwardsCompatibility}}} itself - see comments in the source for more information.
  
- There is a script ({{{dev-tools/scripts/addBackcompatIndexes.py}}}) that automates most of the process: it downloads the source for the specified release; generates indexes for the current release using {{{TestBackwardsCompatibility}}}; compresses the indexes and places them in the correct place in the source tree; modifies {{{TestBackwardsCompatibility.java}}} to include the generated indexes in the list of indexes to test; and then runs {{{TestBackwardsCompatibility}}}.  Run this script on the stable branch and on the unstable branch, and if the current release is a bugfix release, also on the release branch.  On each branch, after running the script, {{{git add}}} the generated indexes, then {{{cd lucene/backwards-codecs}}} and run {{{ant test -Dtestcase=TestBackwardsCompatibility}}} and make sure passes before running {{{git commit}}} and {{{git push}}}.
+ There is a script ({{{dev-tools/scripts/addBackcompatIndexes.py}}}) that automates most of the process: it downloads the source for the specified release; generates indexes for the current release using {{{TestBackwardsCompatibility}}}; compresses the indexes and places them in the correct place in the source tree; modifies {{{TestBackwardsCompatibility.java}}} to include the generated indexes in the list of indexes to test; and then runs {{{TestBackwardsCompatibility}}}.  Run this script on the stable branch, the unstable branch, and on the release branch.  On each branch, after running the script, {{{git add}}} the generated indexes, then {{{cd lucene/backwards-codecs}}} and run {{{ant test -Dtestcase=TestBackwardsCompatibility}}} and make sure passes before running {{{git commit}}} and {{{git push}}}.
  
- {{{TestBackwardsCompatibility}}} will not test indexes for {{{Version.LATEST}}}, and will fail if it finds indexes from that version, so before you run {{{addBackcompatIndexes.py}}}, make sure {{{dev-tools/scripts/addVersion.py}}} has been run with the next version to be released on each of the branches - see item #3, about adding a new version, in the [[#Branching_.26_Feature_Freeze|Branching & Feature Freeze]] section, above.  This will likely only be an issue on the release branch, if the current release is a bugfix release, since {{{addVersion.py}}} will have already been run on the stable branch and on the unstable branch '''before''' the release process has gotten to this point.
+ {{{TestBackwardsCompatibility}}} will not test indexes for {{{Version.LATEST}}}, and will fail if it finds indexes from that version, so before you run {{{addBackcompatIndexes.py}}}, make sure {{{dev-tools/scripts/addVersion.py}}} has been run with the next version to be released on each of the branches - see item #3, about adding a new version, in the [[#Branching_.26_Feature_Freeze|Branching & Feature Freeze]] section, above.
  
  To print the script's usage, run it with the {{{--help}}} option: {{{python3 -u dev-tools/scripts/addBackcompatIndexes.py --help}}}