Author: buildbot
Date: Mon Sep 14 16:53:49 2015
New Revision: 965403
Log:
Staging update by buildbot for oodt
Modified:
websites/staging/oodt/trunk/content/ (props changed)
websites/staging/oodt/trunk/content/development.html
Propchange: websites/staging/oodt/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 14 16:53:49 2015
@@ -1 +1 @@
-1702815
+1702994
Modified: websites/staging/oodt/trunk/content/development.html
==============================================================================
--- websites/staging/oodt/trunk/content/development.html (original)
+++ websites/staging/oodt/trunk/content/development.html Mon Sep 14 16:53:49
2015
@@ -45,7 +45,18 @@ under the License.
<body>
<!-- MAIN .MD CONTENT -->
- <!-- HEADER
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!-- HEADER
================================================== -->
<div class="row">
@@ -108,83 +119,8 @@ under the License.
<div class="subProductWrapper"><div class="subProductHeader"><h3
id="productSubheadSlot">How we keep OODT alive and kicking</h3></div></div><div
class="visualContentWrapper"><div class="contentGradient"></div><div
id="content"><div class="diptych triptychSpace"><div class="visualPadding"
id="leftPlate"><p class="callout">
Like many open source projects, Apache OODT is continually being
developed and improved upon
by its devoted team members.
- </p><p>
- <strong>Version 0.7</strong> has been released and is avaiable for
download and use.
- This is a <b>large</b> release and it is recommended that all users
of any prior version of
- OODT upgrade immediately to 0.7. Users can easily jump from 0.3
(stable production version) to
- 0.7 and/or from 0.6 to 0.7 with ease. The 0.7 release addresses <a
href="http://s.apache.org/cf0";>79 issues</a>
- from our <a href="http://issues.apache.org/jira/browse/OODT";>JIRA
management system</a>.
-
- This release provides a backwards compatible CAS-PGE upgrade
allowing the wrapper to be used with
- existing config files. 0.7 fixes some bugs in Ganglia support and
allows the Resource Manager to work without Ganglia
- being present. This version also makes significant fixes to File
- Manager tests, provides a Vagrant version of OODT RADIX and upgrades
- RADIX to include CAS-PGE support. This version also includes
- improved support for a new JAX-RS CAS product service, and this
- version eliminates several bugs in the workflow manager in its
- support for dynamic workflow instances.
- </p><p>
- <strong>Version 0.6</strong> has been released and is available for
download and use.
- This is a <b>mid-sized</b> release and it is recommended that all
users of 0.5 upgrade
- immediately to 0.6. The 0.6 release addresses <a
href="http://s.apache.org/6OV";>69 issues</a>
- from our <a href="http://issues.apache.org/jira/browse/OODT";>JIRA
management system</a>.
-
- The release includes full support for the PEAR packaging system for
PHP, including the
- delivery of several PHP PEAR libraries for OODT's file manager. In
addition, this release marks
- the beginnings of several Google Summer of Code projects including
the ability to use Ganglia as a
- resource monitoring system and an all CXF based CAS-product web app.
In addition, Apache OODT 0.6
- now successfully builds with Maven3. The Apache OODT OPSUI got a
facelift in its default skin, new
- CAS-PGE input file writers based on templates have been added,
support for running CAS-PGE in Cygwin
- on Windows has landed, and overall the OODT RADIX installer has been
significantly improved.
- </p><p>
- <strong>Version 0.5</strong> has been released and is available for
download and use.
- This is a <b>mid-sized</b> release and it is recommended that all
users of 0.4 upgrade
- immediately to 0.5. The 0.5 release addresses <a
href="http://s.apache.org/PY9";>61 issues</a>
- from our <a href="http://issues.apache.org/jira/browse/OODT";>JIRA
management system</a>.
-
- The release includes various ingestion and curation-related
improvements to our File Manager
- system including a lenient Lucene-based catalog that allows the
ingestion of arbitrary metadata;
- improvements to our Solr-based indexing system to dump File Manager
metadata from arbitrary catalog
- backends to Solr; and improvements to our Curator JAX-RS web
application system.
-
- In addition, several bugs related to the PushPull remote file
retrieval
- system and bugs related to various tools including the ExpImpCatalog
tool
- were fixed.
-
- Finally the release marks a complete improvement of the WEngine
workflow
- system. CAS-PGE, crawler, workflow manager and resource manager can
now all
- be used together, in a forwards (Wengine/Workflow2) and backwards
- compatible way. Early WEngine features including explicit support for
- branch and bounds in policy, inheritable configuration, global
workflow
- conditions, task-level timeouts and post conditions, are now all
supported.
- </p><p>
- <strong>Version 0.4</strong> has been released and is available
for download and use. This is
- a <b>major</b> release that includes <a
href="http://s.apache.org/uGQ";>168 fixed issues in JIRA</a>
- and is now the major recommended release of OODT to be using. One
major note is that
- the updates to the workflow manager (described in <a
href="https://issues.apache.org/jira/browse/OODT-215";>OODT-215</a>)
- are not yet fully complete. Instead of waiting for them to finish,
we rolled this release and are
- recommending users to stay on the 0.3 version of the workflow
manager, cas-pge, and the
- crawler components. All other components should be upgraded to
their 0.4 counterparts. A complete list of changes
- can be found <a
href="http://www.bizdirusa.com/mirrors/apache//oodt/CHANGES-0.4.txt";>here</a>.
- Grab your copy from the <a href="../downloads">Download</a> page
today.
- </p><p>
- <strong>Version 0.3</strong> has been released and is available
for download and use. This is the
- second release from the team as a Top Level Project and includes
several bug fixes and
- enhancements, over 50 issues were closed during this release
cycle. A complete list of changes
- can be found <a
href="http://www.bizdirusa.com/mirrors/apache//oodt/CHANGES-0.3.txt";>here</a>.
- Grab your copy from the <a href="../downloads">Download</a> page
today.
- </p><p>
- The Apache OODT community is proud to present version 0.2 for
download and use. This is the
- first release from the team as a Top Level Project, which
demonstrates our commitment to continuous
- improvement. Be sure to visit the <a
href="../downloads">Download</a> page to get a copy for yourself.
- </p><p>
- The OODT Team has graduated from the <a
href="http://incubator.apache.org/";>Incubator</a> and we
- are pleased to inform you that our code is available for <a
href="../downloads">download</a>.
- We've developed a <a href="roadmap">roadmap</a> outlining future
releases, including
- the first release under Apache aegis: 0.1-incubating, which we
hope to offer for
- download shortly. Of course, there's nothing stopping an early
- adopter from grabbing <a href="source">the source</a> and building
it him or herself.
- </p><h4>Build Details</h4><p>
+ </p>
+ <h4>Build Details</h4><p>
The majority of the <a href="../components">components</a> of OODT
is written in
<a href="http://java.sun.com/";>Java</a>, while the <a
href="../components/agility">Agility</a>
component is written in <a href="http://python.org/";>Python</a>.
Knowledge of both is nice, though.
@@ -198,11 +134,7 @@ under the License.
to include a lot of automated unit and functional testing. Apache
OODT has its own
<a href="https://builds.apache.org/job/oodt-trunk/";>Jenkins
continuous integration</a>
server that runs nightly, and automatically after each commit.
- </p></div>
-
-<div class="visualClear"></div>
-
-<p></div><div class="triptychRight"><div class="columnBorder"><div
class="visualPadding" id="rightPlate"><div id="sidebar">
+ </p></div><div class="visualClear"></div></div><div
class="triptychRight"><div class="columnBorder"><div class="visualPadding"
id="rightPlate"><div id="sidebar">
<h4>Developer Details</h4>
<ul><li><a href="#">Roadmap</a> to future releases</li>
<li><a
href="http://issues.apache.org/jira/browse/OODT";>Bug</a> and other issue
reports</li>
@@ -212,13 +144,15 @@ under the License.
<li><a
href="http://svn.apache.org/viewvc/oodt/";>ViewVC</a> repository viewer</li>
</ul></li>
<li><a href="../contact">Mailing lists</a></li>
- <li><a
href="https://cwiki.apache.org/confluence/display/OODT/Home";>Wiki</a></li>
<br />
+ <li><a
href="https://cwiki.apache.org/confluence/display/OODT/Home";>Wiki</a></li>
</ul><h4>Additional Resources</h4>
<ul><li><a href="../components">Component</a> structure</li>
<li><a href="https://cwiki.apache.org/OODT/home.html";>OODT
Wiki</a></li>
- </ul></div></div></div></div></div></div><div style="clear:
both;"> </div></p>
-<p></div>
-</div></p>
+ </ul></div></div></div></div></div></div><div style="clear:
both;"> </div>
+
+</div>
+
+</div>
<div id="footer">
