svn commit: r1412700 - /airavata/site/trunk/content/development/roadmap.mdtext

[sm...@apache.org]

Author: smarru
Date: Thu Nov 22 22:51:05 2012
New Revision: 1412700

URL: http://svn.apache.org/viewvc?rev=1412700&view=rev
Log:
adding more detiails to roadmap

Modified:
    airavata/site/trunk/content/development/roadmap.mdtext

Modified: airavata/site/trunk/content/development/roadmap.mdtext
URL: http://svn.apache.org/viewvc/airavata/site/trunk/content/development/roadmap.mdtext?rev=1412700&r1=1412699&r2=1412700&view=diff
==============================================================================
--- airavata/site/trunk/content/development/roadmap.mdtext (original)
+++ airavata/site/trunk/content/development/roadmap.mdtext Thu Nov 22 22:51:05 2012
@@ -16,12 +16,28 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-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.
+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.
 
 ![Airavata Agile Development](/images/agile-development.png "Airavata Agile Development")
 
-For detailed feature list, please see the release notes for individual [releases][downloads].
+The development process is to emphasise:
+
+* Individuals and interactions over processes and tools
+
+* Working software over comprehensive documentation
+
+* Customer collaboration over contract negotiation
+
+* Responding to change over following a plan
+
+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.
+
+For detailed apache airavata feature list, please see the release notes for individual [releases][downloads].
 
 Please communicate your feedback, and requirements through the mailing lists and JIRA.
 
+The above development philosophy is based on:
+
+*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.* 
+
 [downloads]: /about/downloads.html
\ No newline at end of file