lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by ShawnHeisey
Date Wed, 20 Sep 2017 21:13:46 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 ShawnHeisey:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=259&rev2=260

Comment:
Add note about the RedirectMatch line for the Solr reference guide, so that the redirect is
not updated prematurely.

  
  == Push docs, changes and javadocs to the CMS production tree ==
  
-  1. Ensure your refridgerator has at least 2 beers - the svn import operation can take a
while, depending on your upload bandwidth.  (Data point: on a 5Mbps upload connection, it
took me 11 minutes to upload the Lucene docs and 6 minutes to upload the Solr docs. - Steve)
 
+  1. Ensure your refridgerator has at least 2 beers - the svn import operation can take a
while, depending on your upload bandwidth.  (Data point: on a 5Mbps upload connection, it
took me 11 minutes to upload the Lucene docs and 6 minutes to upload the Solr docs. - Steve)
   1. Go to the checkout directory where you have built the release and push the documentation
via subversion import. Before doing this make sure that the Javadocs are correctly built (if
not rebuild with {{{ant documentation -Dversion=X.Y.Z}}} from the release tag created above,
be sure to check that the version number is correct before pushing).  Example:
   {{{
  svn -m "Add docs, changes and javadocs for Lucene 6.0.1" import <checkoutroot>/lucene/build/docs
https://svn.apache.org/repos/infra/websites/production/lucene/content/core/6_0_1
@@ -242, +242 @@

   1. Click on the CMS book marklet on your bookmarks bar. If you have not already installed
the bookmark, go to  [[https://cms.apache.org/#bookmark|CMS bookmarklet page]] and search
for the link "ASF CMS" and follow the instructions.
   1. Before changing anything here, click {{{[Update this directory]}}} to ensure you are
operating on the latest version of the website.
   1. Scroll down to the file {{{.htaccess}}} and click {{{[Edit]}}}
-  1. Locate the three lines starting with {{{RedirectMatch temp /core|solr/api/...}}} and
change the version url component to match {{{X_Y_Z}}} above. Click {{{Submit}}}
+  1. Locate the lines starting with {{{RedirectMatch temp /core|solr/api/...}}} and change
the version url component to match {{{X_Y_Z}}} above. One of the RedirectMatch lines will
be for the Solr reference guide, and will only have X_Y instead of X_Y_Z.  That line should
only be updated if a new reference guide is being released at the same time as this release.
+  1. Click {{{Submit}}}.
   1. Click {{{Commit}}}, fill in a message and commit your change. No need to publish site
yet - that will be done in next chapter.
  
  '''NOTE''' As an alternative to CMS online editing, you can checkout the site from SVN and
edit/commit {{{.htaccess}}} that way.
@@ -256, +257 @@

    * Convert the Solr quickstart tutorial to a form usable on the website and copy it into
place in a local CMS svn checkout and then svn commit:
      {{{
  tar xvfz solr-6.4.0-src.tgz   # Unpack the Solr source distribution
- cd solr-6.4.0/solr             
+ cd solr-6.4.0/solr
  ant generate-website-quickstart
  cp build/website/quickstart.mdtext <lucene-cms-trunk-dir>/content/solr/quickstart.mdtext
  }}}
@@ -299, +300 @@

  
  Mails to the announce@apache.org list must be sent from an @apache.org email address and
should contain a signature.
  
- Because you're likely not subscribed to the general, dev, and -user lists with your @apache.org
address, sending the announcement email to those list with your @apache.org address will need
to be moderated through, which will likely result in delayed transmission.  To avoid this,
send the emails these lists using your subscribed email address, and then separately send
the announcements to announce@apache.org . 
+ Because you're likely not subscribed to the general, dev, and -user lists with your @apache.org
address, sending the announcement email to those list with your @apache.org address will need
to be moderated through, which will likely result in delayed transmission.  To avoid this,
send the emails these lists using your subscribed email address, and then separately send
the announcements to announce@apache.org .
  
  Note: Copy-pasting from the release notes into Gmail might sometimes make Gmail (or any
other client) send it as HTML formatted, which can break at the mailing list bot. Better to
copy-paste the raw/edit text.
  
@@ -316, +317 @@

  {{{
  python3 -u -B dev-tools/scripts/releasedJirasRegex.py 6.6.0 lucene/CHANGES.txt
  
- python3 -u -B dev-tools/scripts/releasedJirasRegex.py 6.6.0 solr/CHANGES.txt 
+ python3 -u -B dev-tools/scripts/releasedJirasRegex.py 6.6.0 solr/CHANGES.txt
  }}}
  == Increment the version on the release branch ==
  Add the next version after the just-released version on the release branch.

Mime
View raw message