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

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

Comment:
add step to make sure TestBackwardsCompatibility passes before pushing

  == 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 trunk, 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 {{{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 and on trunk, 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}}}.
  
  {{{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 trunk '''before''' the release process has gotten to this point.