[
https://issues.apache.org/jira/browse/AIRAVATA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884703#comment-13884703
]
Suresh Marru commented on AIRAVATA-1000:
----------------------------------------
Summering the previous roadmap mail thread, Key features/issues to resolve are:
* Ready to move into semantic versioning of releases - Agreed upon on thread -
http://markmail.org/thread/d6mx5sk553fkdi43
* Have a API which will survive through minor releases and only calls out for
API changes for major releases - depends on - AIRAVATA-991
* Decide upon a going forward SCM among SVN or GIT - Airavata decided on GIT
and made the transition as of 01/28/2014,
* Have well documented client integration examples
* Scrub of any unused dependencies and revisit the latest versions of critical
dependencies
* Agree upon supported features
* Remove any third party maven repos (down to 1 as of today)
* Resolve all the issues which are bugs (and preferably improvements as well)
* Revisit all wish style issues and comment on the ones planned to be addressed
in near future.
* External review of the project by soliciting developers from fellow apache
projects.
* Improve test coverage - Specifically we need set of tests which actually
execute workflows against stampede, trestles, lonestar etc ...
* Clean up configurations
* Resurrect Jenkins and do proper continuous integration
* Reduce code duplication - E.g :- database connecting code
> Road map to Airavata 1.0
> ------------------------
>
> Key: AIRAVATA-1000
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1000
> Project: Airavata
> Issue Type: Epic
> Reporter: Suresh Marru
> Fix For: 1.0
>
>
> As discussed in detail on the thread
> http://markmail.org/thread/5nq7jfk5b7izbip3 target 1.0 release of Airavata.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
