[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=237&rev2=238

Comment:
Added vertical whitespace to a couple examples; moved point-release CHANGES.txt sync from publishing section to post-release section; converted more revision numbers to ellipses

  = Repeat if Needed =
  Should any issues be discovered, allow fixes to be committed to the release branch, and once complete, rerun tests, produce a new RC and call another vote, as described in the previous sections.
  
- = Publishing to the ASF Mirrors =
+ = Publishing to the ASF Mirrors and to Maven Central =
  Once [[http://www.apache.org/foundation/voting.html#ReleaseVotes|three PMC members have voted for a release]], it may be published. You should wait at least 72 hours, not including weekend days. For instance, if you announce the RC on Friday, give until end of day Tuesday or Wednesday morning for the vote.
  
   1. Announce that the vote has passed on the dev mailing list, ideally with subject beginning [RESULT]
   1. Tag the release from the same revision from which the passing release candidate's was built:
   {{{
  git tag -a releases/lucene-solr/5.5.0 -m "Lucene/Solr 5.5.0 release" 2a228b3920a07f930f7afb6a42d0d20e184a943c
+ 
  git push origin releases/lucene-solr/5.5.0
  }}}
- 
-  1. If this is a point release, copy the CHANGES.txt entry for this point release back to the stable and unstable branches' CHANGES.txt files, removing any duplicate entries  (i.e., each issue should appear only once, in the earliest point-release that contains the fix, on the assumption that all future releases also contain the fix).
   1. Delete the maven artifacts from the staging repo:
   {{{
- svn rm -m "delete the lucene maven artifacts" https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev1672403/lucene/maven
+ svn rm -m "delete the lucene maven artifacts" https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev.../lucene/maven
+ 
- svn rm -m "delete the solr maven artifacts" https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev1672403/solr/maven
+ svn rm -m "delete the solr maven artifacts" https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev.../solr/maven
  }}}
   1. Move the new release artifacts to the release repo:
   {{{
- svn move -m "Move Lucene RC2 to release repo." https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev1672403/lucene https://dist.apache.org/repos/dist/release/lucene/java/5.1.0
+ svn move -m "Move Lucene RC2 to release repo." https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev.../lucene https://dist.apache.org/repos/dist/release/lucene/java/5.1.0
+ 
- svn move -m "Move Solr RC2 to release repo." https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev1672403/solr https://dist.apache.org/repos/dist/release/lucene/solr/5.1.0
+ svn move -m "Move Solr RC2 to release repo." https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.1.0-RC2-rev.../solr https://dist.apache.org/repos/dist/release/lucene/solr/5.1.0
  }}}
   1. Note at this point you will see the Jenkins job "Lucene-Solr-SmokeRelease-master" begin to fail, until you run the "Generate Backcompat Indexes" steps below!
   1. Publish maven artifacts - from the {{{lucene/}}} directory in a source checkout (note that this step will prompt you for your apache credentials):
@@ -192, +193 @@

  
  ant clean stage-maven-artifacts -Dmaven.dist.dir=/tmp/releases/6.0.1/lucene-solr-6.0.1-RC2-rev.../solr/maven/ -Dm2.repository.id=apache.releases.https -Dm2.repository.url=https://repository.apache.org/service/local/staging/deploy/maven2
  }}}
-  1. Once you have published the resources to repository.apache.org, you will need to log in there with your ASF credentials, locate the release that you just uploaded, "close" and then "release" the artifacts. This will cause them to sync to Maven Central.  See [[PublishMavenArtifacts|here]]  for more details.
+  1. Once you have transferred all maven artifacts to repository.apache.org, you will need to: log in there with your ASF credentials; locate the staging repository containing the release that you just uploaded; "close" the staging repository; and then "release" the staging repository.  This will cause them to sync to Maven Central.  See [[PublishMavenArtifacts|here]]  for more details.
   1. Maven central should show the release after a short while, but you need to wait 24 hours to give the Apache mirrors a chance to copy the new release.
   1. If you wish, use this script to continually check the number and percentage of mirrors (and Maven Central) that have the release: {{{dev-tools/scripts/poll-mirrors.pl -version 5.5.0}}}.
  
@@ -279, +280 @@

   1. Add the new version to Wikipedia (english and maybe your own language)
  
  = Post-Release =
+ == Synchronize CHANGES.txt ==
+ 
+ If this is a point release, copy the CHANGES.txt section for this point release back to the stable and unstable branches' CHANGES.txt files, removing any duplicate entries, but *only from sections for as-yet unreleased versions*; leave intact duplicate entries for already-released versions.
+ 
  == 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.
  
@@ -341, +346 @@

   1. Do another JIRA search in both Solr and Lucene to find all issues with Unresolved Resolution and fixVersion of the release you just made (this URL may work - but edit the fixVersion part - https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE,SOLR)+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.
  
- == Don't mirror old releases ==
+ == 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.
  
  Here's an example for the 6.0.1 release (note that the 5.5.1 release is not removed):