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

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

Comment:
Updated the "Update Version Numbers in the Source Code" section for bug fix releases to bump the version on non-release branch post-release.

    * If a bugfix release, start on the release branch:
     * {{{ python3 -u dev-tools/scripts/addVersion.py X.Y.Z }}}
     * {{{ git add -u .; git commit; git push }}}
+    * Note the commit hash here as you would need this in the post-release step for incrementing the version number on non-release branches. (Check out the post-release section for more information)
-    * Using the commit id from the previous commit, run {{{addVersion.py}}} on the stable branch, adding {{{ --changeid ID }}}
-    * {{{ git add -u .; git commit; git push }}}
-    * Run {{{addVersion.py}}} on trunk, modifying the stable branch command with the new change id and path to the stable branch checkout.
-    * {{{ 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.
    * If a minor release, start on the stable branch:
     * {{{ python3 -u dev-tools/scripts/addVersion.py X.Y+1.0 }}}
     * {{{ git add -u .; git commit; git push }}}
@@ -292, +288 @@

   1. Add the new version to Wikipedia (english and maybe your own language)
  
  = Post-Release =
+ == Update Version Numbers in the Source Code - For non-release branch ==
+  1. If this is a bug fix release, increment the version number on non-release branch now, right before adding the back-compat index. You may see a build failure email between committing and pushing this and pushing the back-compat indexes (next step).
+    * Using the commit id from the previous commit, run {{{addVersion.py}}} on the stable branch, adding {{{ --changeid ID }}}
+    * {{{ git add -u .; git commit; git push }}}
+    * Run {{{addVersion.py}}} on trunk, modifying the stable branch command with the new change id and path to the stable branch checkout.
+    * {{{ 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.
+ 
  == 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.