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

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

Comment:
New: Clear Security Level of Public JIRA Issues. (courtesy of Alexandre)

  
  When doing a major version release, eg. 8.0.0, you might also need to reenable some backward compatibility tests for corner cases. To find them, run {{{grep -r assume lucene/backward-codecs/}}}, which should find tests that have been disabled on master because there was no released Lucene version to test against.
  
- == Update JIRA ==
+ == Update JIRA Versions ==
   1. Go to the JIRA "Manage Versions" Administration pages (https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions and https://issues.apache.org/jira/plugins/servlet/project-config/SOLR/versions). 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): (https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE,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".
   1. Do another JIRA search to find all issues with Unresolved Resolution and fixVersion of the release you just made.  Note that Jira can only bulk-change fixVersion if you search only one project at a time.  This URL may work - but edit the fixVersion part, and change LUCENE to SOLR to get to Solr's issues separately - https://issues.apache.org/jira/issues/?jql=project+=+LUCENE+AND+resolution=Unresolved+AND+fixVersion=6.0.1, and do a bulk change to the fixVersion to be both the master version and the next version on the branch you just released from.  Uncheck the box that says "send an email for these changes".
   1. Add a new Version for the next possible release version on the "Manage Versions" Administration page (https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions). e.g. If the current release is 5.2.1, add 5.2.2 with a description so that contributors can commit to the release branch with the next release version. In case of a minor release e.g. 5.2, this step needs to be done when the new release branch is cut.
  
+ == Clear Security Level of Public JIRA Issues ==
  
+ ASF JIRA has a deficiency in which issues that have a security level of "Public" are nonetheless not searchable.  Lets do a cleanup task now, even though it's not strictly release related:
+ 
+  1. It is a bit hard to find all Public issues as Security level is not
+ in the dropdowns. So, the search query has to be in the advanced mode
+ and be: project = SOLR AND Level = "Public"
+  1. Can only be done maximum 1000 issues at a time (under Tools/Bulk Change)
+  1. Check Edit
+  1. Set Security Level to None, scroll down all the way and uncheck
+ Send email, then submit
+  1. Confirm
+  1. Wait (approx 7min per 1000)
+  1. Acknowledge
  
  == Stop mirroring old releases ==
  Shortly after new releases are first mirrored, they are automatically copied to the archives.  Only the latest point release from each active branch should be kept under the Lucene PMC svnpubsub area {{{dist/releases/lucene/}}} and {{{dist/releases/solr/}}}.  Older releases can be safely deleted, since they are already backed up in the archives.