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] Trivial Update of "ReleaseTodo" by SteveRowe
Date Tue, 09 Jul 2013 04:14: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 SteveRowe:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=154&rev2=155

Comment:
typo

  
  == Website += javadocs ==
  The problem: Lucene's and Solr's voluminous per-release javadocs break the standard CMS
process for the website (i.e., committer commits to the source tree; the CMS buildbot generates
the site, then commits to the staging tree; committer reviews and then publishes to the production
tree), because dynamic website updates, currently scheduled at 21 minutes after the hour on
the hour, interrupt the extremely long commit times for javadocs being staged by buildbot,
resulting in failed commits, caused by conflicts with the dynamic updates: by the time the
buildbot-triggered commit has finished, its svn tree has been rendered stale.
+ 
- deThe solution: skip committing javadocs to the source tree, then staging, then publishing,
and instead commit javadocs directly to the production tree.  Ordinarily this would be problematic,
because the CMS wants to keep the production tree in sync with the staging tree, so anything
it finds  in the production tree that's not in the staging tree gets nuked.  However, the
CMS has a built-in mechanism to allow exceptions to the keep-production-in-sync-with-staging
rule: {{{extpaths.txt}}}.
+ The solution: skip committing javadocs to the source tree, then staging, then publishing,
and instead commit javadocs directly to the production tree.  Ordinarily this would be problematic,
because the CMS wants to keep the production tree in sync with the staging tree, so anything
it finds  in the production tree that's not in the staging tree gets nuked.  However, the
CMS has a built-in mechanism to allow exceptions to the keep-production-in-sync-with-staging
rule: {{{extpaths.txt}}}.
  
  {{{extpaths.txt}}} lists paths in the production tree, relative to the project website's
root directory, that are allowed to be out of sync with the staging tree.
  

Mime
View raw message