lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by jpountz
Date Mon, 03 Jul 2017 17:14:40 GMT
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 jpountz:

add note about special bw tests that need reenabling upon releasing a new major version

  git commit -m "Add 6.0.0 back compat test indexes"
  git push
+ When doing a major version release, eg. 7.0.0, you might also need to reenable some backward
compatibility tests for corner cases. To find then, run {{grep -r assume lucene/backward-codecs/}},
which should find tests that have been disabled on master due to the fact that there was no
released Lucene version to test against.
  == Update JIRA ==
   1. Go to the JIRA "Manage Versions" Administration pages (
and Next to
the version you'll release, click the gear pop-up menu icon and choose "Release".  It will
ask you for the release date -- enter it.  It will give the option of transitioning issues
marked fix-for the released version to the next version, but do '''not''' do this as it will
send an email for each issue -- we'll address that separately.
   1. Go to JIRA search in both Solr and Lucene and find all issues that were fixed in the
release you just made, whose Status is Resolved.  This URL may work (but edit the fixVersion
part): (,SOLR)+AND+status=Resolved+AND+fixVersion=6.0.1).
 Do a bulk change (Under Tools... menu) to close all of these issues (this is a workflow transition
task). Uncheck the box that says "send an email for these changes".

View raw message