Mailing-List: contact commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Thu, 19 Feb 2015 19:04:15 -0000
Message-ID: <20150219190415.7043.68138@eos.apache.org>
Subject: 
 =?utf-8?q?=5BLucene-java_Wiki=5D_Update_of_=22ReleaseTodo=22_by_AnshumGup?=
 =?utf-8?q?ta?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" f=
or change notification.

The "ReleaseTodo" page has been changed by AnshumGupta:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=3Ddiff&rev1=3D179&re=
v2=3D180

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 ne=
ed committer rights for some of the steps to create an official release). I=
t does not reflect official release policy - many of the items may be optio=
nal, or may be modified as necessary.  =

+ This page is to help a Lucene/Solr committer create a new release (you ne=
ed committer rights for some of the steps to create an official release). I=
t does not reflect official release policy - many of the items may be optio=
nal, or may be modified as necessary.
  =

  See the [[http://www.apache.org/dev/release.html|ASF Releases Policy page=
]].
  =

@@ -87, +87 @@

  =

  =3D Testing the Release artifacts =3D
  =

-  1. There is a script in SVN to do automated checks on a release candidat=
e, e.g. =

+  1. There is a script in SVN to do automated checks on a release candidat=
e, e.g.
  {{{
  python3.2 -u dev-tools/scripts/smokeTestRelease.py http://people.apache.o=
rg/~whoever/4.4.0rc8-rev5551212
- }}} =

+ }}}
  =

  =3D Publishing =3D
  Once [[http://www.apache.org/foundation/voting.html#ReleaseVotes|three PM=
C 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=3Dimmediates https://svn.apache.org/repos/infra/web=
sites/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 sol=
r-X.Y.Z
   1. {{{cd website-production; svn update --depth=3Dimmediates 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 @@

  =

  =3D=3D Update the rest of the website =3D=3D
  =

- '''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 min=
or changes and news blurbs and stuff.
@@ -204, +204 @@

  =

  =3D=3D Don't mirror old releases =3D=3D
  =

- Shortly after new releases are first mirrored, they are copied to the arc=
hives.  Only the latest point release from each active branch should be kep=
t under the Lucene PMC svnpubsub area {{{dist/releases/lucene/}}}.  Older r=
eleases 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 arc=
hives.  Only the latest point release from each active branch should be kep=
t under the Lucene PMC svnpubsub area {{{dist/releases/lucene/}}}.  Older r=
eleases 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/luc=
ene/java/}}} and {{{dist/releases/lucene/solr/}}}, then {{{svn commit}}}.
 =20