[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=179&rev2=180

Comment:
Fixing the instructions for pushing javadocs to the CMS production tree

- This page is to help a Lucene/Solr committer create a new release (you need committer rights for some of the steps to create an official release). It does not reflect official release policy - many of the items may be optional, or may be modified as necessary.  
+ This page is to help a Lucene/Solr committer create a new release (you need committer rights for some of the steps to create an official release). It does not reflect official release policy - many of the items may be optional, or may be modified as necessary.
  
  See the [[http://www.apache.org/dev/release.html|ASF Releases Policy page]].
  
@@ -87, +87 @@

  
  = Testing the Release artifacts =
  
-  1. There is a script in SVN to do automated checks on a release candidate, e.g. 
+  1. There is a script in SVN to do automated checks on a release candidate, e.g.
  {{{
  python3.2 -u dev-tools/scripts/smokeTestRelease.py http://people.apache.org/~whoever/4.4.0rc8-rev5551212
- }}} 
+ }}}
  
  = Publishing =
  Once [[http://www.apache.org/foundation/voting.html#ReleaseVotes|three PMC members have voted for a release]], it may be published.
@@ -148, +148 @@

  repository automatically.
   1. Ensure your refridgerator has at least 4 beers.
   1. {{{svn co --depth=immediates https://svn.apache.org/repos/infra/websites/production/lucene/content/ website-production}}}
-  1. untar the release.tgz to create releaseX_Y_Z/
+  1. untar the lucene and solr release .tgz to create lucene-X.Y.Z and solr-X.Y.Z
   1. {{{cd website-production; svn update --depth=immediates core solr; cd ..}}}
-  1. {{{cp -r releaseX_Y_Z/lucene/docs website-production/core/X_Y_Z}}}
+  1. {{{cp -r lucene-X.Y.Z/docs website-production/core/X_Y_Z}}}
   1. {{{svn add core/X_Y_Z}}}
   1. {{{svn commit # this might take some time: ~ 3 beers}}}
-  1. {{{cp -r releaseX_Y_Z/solr/docs website-production/solr/X_Y_Z}}}
+  1. {{{cp -r solr-X.Y.Z/docs website-production/solr/X_Y_Z}}}
   1. {{{svn add solr/X_Y_Z}}}
   1. {{{svn commit # this might take some time: ~ 1 beer}}}
   1. Confirm you can browse to these directories manually, and especially that solr javadocs link back to lucene's correctly.
@@ -171, +171 @@

  
  == Update the rest of the website ==
  
- '''NOTE''': don't do this until you are ready to go to production. Every hour at :21 (e.g. 8:21, 9:21, ...) buildbot will 
+ '''NOTE''': don't do this until you are ready to go to production. Every hour at :21 (e.g. 8:21, 9:21, ...) buildbot will
  commit all content from staging to production.
  
   1. Once mirrors are ready, use the bookmarklet or whatever to do the minor changes and news blurbs and stuff.
@@ -204, +204 @@

  
  == Don't mirror old releases ==
  
- Shortly after new releases are first mirrored, they are 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/}}}.  Older releases can be safely deleted from {{{dist/releases/lucene/}}}, since these releases are already backed up in the archives.  
+ Shortly after new releases are first mirrored, they are 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/}}}.  Older releases can be safely deleted from {{{dist/releases/lucene/}}}, since these releases are already backed up in the archives.
  
  {{{svn remove}}} old releases, including X.Y-1, from {{{dist/releases/lucene/java/}}} and {{{dist/releases/lucene/solr/}}}, then {{{svn commit}}}.