Author: buildbot
Date: Thu Nov 22 22:51:12 2012
New Revision: 839231
Log:
Staging update by buildbot for airavata
Modified:
websites/staging/airavata/trunk/content/ (props changed)
websites/staging/airavata/trunk/content/development/roadmap.html
Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 22 22:51:12 2012
@@ -1 +1 @@
-1412691
+1412701
Modified: websites/staging/airavata/trunk/content/development/roadmap.html
==============================================================================
--- websites/staging/airavata/trunk/content/development/roadmap.html (original)
+++ websites/staging/airavata/trunk/content/development/roadmap.html Thu Nov 22
22:51:12 2012
@@ -89,10 +89,28 @@
<div id="content">
<h1 class="title">Airavata Roadmap</h1>
- <p>Apache Airavata roadmap will always be evolving. The development
process is very agile with continous interaction and feedback from the
community. The following figure illustrate the Airavata's iterative and
incremental development.</p>
+ <p>Apache Airavata roadmap will always be evolving. The development
process is very agile with continous interaction and feedback from the
community. The following figure illustrates Airavata's iterative and
incremental development.</p>
<p><img alt="Airavata Agile Development" src="/images/agile-development.png"
title="Airavata Agile Development" /></p>
-<p>For detailed feature list, please see the release notes for individual <a
href="/about/downloads.html">releases</a>.</p>
+<p>The development process is to emphasise:</p>
+<ul>
+<li>
+<p>Individuals and interactions over processes and tools</p>
+</li>
+<li>
+<p>Working software over comprehensive documentation</p>
+</li>
+<li>
+<p>Customer collaboration over contract negotiation</p>
+</li>
+<li>
+<p>Responding to change over following a plan</p>
+</li>
+</ul>
+<p>Airavata Community comprises of project management committee/committers,
contributors and user community. The community inputs new features,
improvements as epics, which are essentially use cases that need to be further
analyzed. The epics or larger use cases are further broken into manageable
stories. Based on developer interests and active community requests, the
stories are prioritized and tagged to a upcoming release. The release manager
initiates a list of features and bug fixes and community responds by
highlighting pending JIRA's to fix in the release. Once the release is planned,
the design, development and release cycle spins through a next iteration.</p>
+<p>For detailed apache airavata feature list, please see the release notes for
individual <a href="/about/downloads.html">releases</a>.</p>
<p>Please communicate your feedback, and requirements through the mailing
lists and JIRA.</p>
+<p>The above development philosophy is based on:</p>
+<p><em>Agile Manifesto Copyright 2001: Kent Beck, Mike Beedle, Arie van
Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning,
Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C.
Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas.</em> </p>
</div>
<!--<div id="rightnav">
